Most foreign IT companies approaching Belarus’s High-Tech Park treat the business plan as paperwork — a template to populate on the way to a 1% tax regime. That assumption is the single most reliable predictor of a difficult admission. The HTP business plan is not a registration form. It is the document on which a state body forms a judgment about whether your company belongs in the Park at all, and reviewers read it looking for substance that a well-formatted template does not automatically supply.
Understanding what those reviewers actually assess — and, just as importantly, where applications quietly fall apart — turns a stressful, uncertain process into a predictable one. Here is what the Supervisory Board weighs, and the failure modes that most often end in refusal.
Who reads the plan, and against what standard
Admission to the HTP is decided in two stages, by two different bodies. First, the Secretariat of the Supervisory Board carries out a preliminary assessment of the application and a scientific and technical review of the submitted business project, then forwards its recommendation to the Board. The Supervisory Board — which brings together representatives of government agencies and the scientific community, and is accountable to the Council of Ministers — takes the final decision by a simple majority of votes: to register the applicant as a resident, or to refuse.
That structure matters, because the two stages test different things. The Secretariat’s scientific and technical review is where the technical credibility of your project is scrutinised. The Board’s vote is where a broader, and more discretionary, question is answered.
The governing standard comes from the Regulations on the Hi-Tech Park, adopted under Decree No. 8 “On the Development of the Digital Economy.” The decision to register or refuse is made “taking into account the importance and significance of the presented business project for the development of new and high technologies.” Read that carefully. The test is not whether your company is a legitimate IT business, nor whether the forms are complete. It is whether the project is significant for the development of high technologies — and the burden of demonstrating that sits with the applicant. That word, significance, is the lens through which every strong application is written and every weak one is refused. It is also worth reviewing the closed list of activities permitted for residents before a single page of the plan is drafted.
What reviewers are actually looking for
Strong applications share a set of qualities that map directly onto how the plan is reviewed. None of them is satisfied by completing the template alone.
A genuine fit with an eligible activity — not an adjacent one. The first thing checked is whether the company’s declared activity sits squarely within the list of activities permitted for residents under Decree No. 8. That list is broad — software development, IT consulting, data processing, AI and machine learning, FinTech, gaming, and more than thirty other categories — but it is a closed list, and “close enough” is not a category. Reviewers look for a precise match between what you actually do and a named eligible activity, described in the language the regime itself uses. Applications that describe a business in the founder’s own commercial vocabulary, rather than mapping it onto the eligible-activity framework, force reviewers to guess — and guessing rarely favours the applicant.
This is where activity profile matters more than founders expect. A B2B SaaS product, a custom-development shop, and a marketplace each map to a different regime path, with different implications for how the plan is framed and how revenue is treated. Getting that classification right at the outset shapes everything downstream.
Demonstrated innovation and high-tech contribution. Because the statutory test turns on significance for the development of new and high technologies, the plan must make an affirmative case for innovation. It is not enough to state that the company writes software; reviewers want to see what is technologically distinctive about the work — the uniqueness of the activity, the competitive advantage of the products the company intends to build as a resident, and the contribution the project makes to the high-technology sector. A plan that reads like a generic services brochure, interchangeable with a hundred others, invites the conclusion that the project is not significant enough to warrant admission. That conclusion is itself a lawful ground for refusal.
A real operating model, not a shell. Reviewers increasingly look for evidence that the company can actually run the activity it describes, rather than merely registering an entity to capture the tax regime. That means a coherent picture of the team and its competence, a credible development roadmap, a headcount plan, and an investment schedule that together read as something the applicant genuinely intends to execute. Establishing a company “for HTP” without a substantive business model behind it tends to produce one of two outcomes: rejection at the application stage, or — worse — admission followed by problems when operations fail to match the declared project.
Financials that hold together. The business plan carries the financial projections, and for newly established Belarusian subsidiaries of foreign companies, historical statements are not required — which places all the weight on the forward-looking model. Reviewers expect a logically structured financial model with a justified economic basis: revenue projections, export volumes, and investment tied to the activity described rather than to optimistic round numbers. One specific and often-missed technical point is that settlements should be presented in foreign currency, including in dealings with Belarusian counterparties. Projections that are internally inconsistent, or disconnected from the operational plan, undercut the credibility of the entire submission. Getting the model right also protects the value of HTP resident status itself, because the revenue categories you set out here determine how the preferential regime later applies to your income.
Corporate transparency, especially for foreign-owned applicants. Foreign ownership is not an obstacle to admission — the Park has been open to international business by design — but foreign-owned projects face heightened documentation and verification requirements. Reviewers weigh the transparency of the corporate structure and compliance with international AML and KYC standards. For crypto, blockchain, and FinTech projects in particular, a clear AML/KYC framework is part of what makes a project read as credible rather than risky.
The failure modes that lead to refusal
The Regulations set out two formal grounds on which the Board may refuse: a negative conclusion from the scientific and technical review of the submitted documents, and the Board’s own assessment that the project is of insufficient importance for the development of new and high technologies. Almost every real-world refusal traces back to one of these two, but they surface through a recognisable set of practical mistakes.
Activity misclassification. The most common reason foreign companies are refused is a mismatch between the project and the eligible-activity list — either a genuine misunderstanding of what qualifies, or an attempt to bring in a business that is not IT-related or not built on high-technology services. It is worth checking a proposed activity against the operations the HTP administration reviews before submission, because describing, even inadvertently, a type of activity not permitted for residents is a direct route to refusal.
The significance gap. A plan can describe a perfectly real, perfectly legal IT business and still be refused because it fails to demonstrate that the project matters for high-technology development. This is the failure mode that surprises applicants most, precisely because the company is legitimate — but legitimacy was never the test the Board applies.
The shell problem. Where the plan reveals an entity with no real operating substance behind it, reviewers are entitled to conclude that the declared activity will not genuinely be carried out — and to refuse on that basis, or to grant status that later becomes a liability.
Procedural defects. A large share of delays and resubmissions come from avoidable document errors: inconsistent dates across the file, missing certified translations, absent notarisation, or an incomplete package. These rarely produce an outright refusal on their own, but they stall the application — and because the Board convenes only about once every three months, a defect that pushes you out of one session can cost a full quarter.
Inaccurate or inconsistent information. Providing inaccurate information is treated seriously, both at admission and afterwards, and inconsistencies between the business plan and the constituent documents erode reviewer confidence in everything else that has been filed.
Beyond admission: the risk that outlasts the decision
It is tempting to treat the Board’s positive decision as the finish line. It is closer to the starting line. The business plan you submit is also an operating commitment: once admitted, the company signs a resident agreement and takes on ongoing duties — quarterly revenue declarations, annual audits, and notifications to the Secretariat about any material change to activities or corporate structure. The Supervisory Board retains jurisdiction to revoke resident status for non-compliance, and for many businesses the loss of status mid-operation — with retrospective recalculation of tax under the general regime — is a larger financial risk than an initial refusal ever was.
That is why the strongest business plans are written to be lived with, not merely approved. The reporting and compliance obligations that begin the day status is granted should shape how the plan is drafted in the first place, so that the declared project and the operating reality stay aligned quarter after quarter.
FAQ
From submission of a complete dossier, the formal review takes up to one month. In practice, the overall timeline runs from roughly six weeks to four months, because the Supervisory Board meets only about once every three months and accumulates applications before each session. The date of the next meeting, and the readiness of your documentation, matter as much as the complexity of the project.
Yes. The Board can review the materials, put questions to the applicant, and request additional data or further expert evaluation before it votes. A prepared applicant treats this as an opportunity to close gaps, not as a sign of trouble.
No — the HTP has traditionally welcomed international business, and foreign participation is not itself a barrier. Foreign-owned projects do face additional documentation and verification requirements, particularly around corporate transparency and AML/KYC, so the bar for a clean, well-evidenced submission is higher.
It is typically no longer than about twenty pages. Length is not the point: the document has to cover activities, product description, target markets, revenue projections, R&D focus, headcount, and investment, and it has to make the innovation case within that space. A concise, well-argued plan reads far better to reviewers than a padded one.
A refusal is not necessarily the end. Because refusals usually stem from identifiable causes — misclassified activity, a weak significance argument, or document defects — the more productive response is to diagnose the specific ground, correct it, and resubmit for a later session rather than reapplying with the same materials.
It is the decisive one, but it sits within a package that also includes the application form, constituent documents with certified translations, founder and director information, and a description of the planned IT activities. Inconsistencies between these documents are themselves a failure mode, so the plan has to be coherent with everything filed alongside it.
Conclusion
The HTP business plan rewards companies that treat it as what it is: a substantive case, made to a state body weighing whether a project genuinely advances high technology in Belarus — not a formality standing between an applicant and a tax rate. The applications that succeed on the first attempt are the ones that map cleanly onto an eligible activity, argue their innovation and significance explicitly, present a real operating and financial model, and stay internally consistent across the whole document package. The ones that fail almost always do so for reasons that were visible in the draft.
Getting it right the first time is largely a matter of writing to the standard reviewers actually apply and anticipating the failure modes above before submission. For companies that would rather not learn those lessons through a refused application, professional HTP business plan preparation pairs a submission-ready document with direct experience of how the Supervisory Board reads it.