Can you build a good house without a blueprint or a plan? Can you estimate the cost of construction without a budget? Of course not, you’d say. Indeed, unless we’re talking about a simple garden shed, no one would even consider building a house without proper planning.
Yet, when it comes to developing mobile and web applications, clients often overlook this crucial stage—project planning. As a result, misunderstandings with developers arise, expectations aren’t met, and the project ultimately fails, leading to wasted time and money.
Below, we’ll share how we create outstanding mobile and web applications while ensuring we meet our clients’ expectations.
At POLYGANT, every project starts with the Discovery Phase. This phase costs $7,000 and takes approximately 100 working hours from our team. It is a mandatory step.
As a result of this phase, we produce a set of documents that describe the future application in detail, including:
Specification (Technical Requirements)
Screen Mockups
Based on this documentation, we provide an estimate for the cost and timeline of the project, which is then sent for approval. Once the estimate is agreed upon, we proceed to project development—the DELIVERY Phase.
⚠️ We do not provide cost and timeline estimates without a detailed Specification prepared by our specialists.
DELIVERY Phase
This is the development stage, where the product is built according to the approved specification. Development is usually divided into 3-4 stages, each with clearly defined progress indicators. Payments can also be structured by stages.
We follow the Agile methodology, working in 2-week sprints. Typically, each sprint results in an updated working version of the project, allowing our clients to monitor progress in real-time.
SUPPORT Phase
Once the product (or MVP) is developed, it moves into the support and maintenance stage. We provide paid support and ongoing improvements for all projects developed by our team with no time limitations.
Important Notes
Our team only takes on projects requiring at least 1,000 working hours. Smaller projects are not of interest to us.
We do not accept urgent projects with unrealistic deadlines (e.g., “it must be done yesterday”). We prioritize quality over speed.
We always work with full or partial (at least 50%) prepayment.
We do not participate in tenders or government procurement.
We do not work with third-party or legacy code—except in cases of refactoring.
DISCOVERY Phase
Just as you can’t build a solid house without blueprints, you can’t develop a high-quality application without a detailed specification.
A Project Specification (also known as a Technical Requirement Document or a Design Document in mobile game development) is the foundation of any successful product. This is why it’s always the first step in our development process.
⚠️ Without a clear specification, it is impossible to accurately estimate the cost and timeline of development.
How We Start
We begin by assembling a working group that includes:
A Client Representative
A Project Manager
A UI Designer
A Business Analyst
Once the team is formed, we schedule an initial call to discuss the client’s vision, preferences, and expectations. During this call, we go over a pre-prepared list of questions to gather all necessary details.
The Project Specification is created using Google Docs, and the client is given real-time access to the document from the start. Screen mockups are designed in Figma, allowing the client to track progress and provide immediate feedback.
⚠️ If needed, we can also involve additional specialists from technical or even legal fields to ensure a well-rounded approach to the project.
What Is a Specification?
A Project Specification (Technical Requirement Document) is a comprehensive document that provides a detailed description of the future product from multiple perspectives:
Conceptual (overall vision and goals)
Usability & User Flows
Technical Requirements
Our specifications often include detailed screen diagrams, making it easier for all stakeholders to understand the product’s structure and functionality.
Why Is a Specification Essential?
The two most critical concerns for any client are cost and timeline. A well-prepared specification helps:
Accurately estimate development costs and deadlines by covering every detail that may impact pricing and timelines.
Align expectations between the client and the development team, preventing misunderstandings that could lead to delays or conflicts.
Define solutions for complex project aspects in advance.
Our specifications are developed by top-tier experts with extensive experience across various industries. Their expertise allows them to identify optimal solutions that others might overlook.
What Does a Specification Include?
While each project is unique, a typical Project Specification consists of the following key sections:
Project Overview – A simple, clear explanation of the product/service, its purpose, and how it works.
Component Structure – Details on all project components: backend, frontend, mobile applications, and how they interact.
Technology Stack – The programming languages, frameworks, and technical requirements.
User Flows & Use Cases – How users will interact with the application, including screen maps and key mockups.
Security & Scalability – Protection against cyber threats, system reliability, and strategies for handling high traffic loads.
A Technical Specification typically ranges from 20 to 40 pages (A4 format), depending on project complexity.
At the end of the specification phase, our team provides a detailed cost estimate and development timeline, ensuring full transparency before moving forward.
DELIVERY Phase
Once the client has approved the cost estimate and timeline, the project has been divided into phases, and the initial payment for the first phase has been received, we move into the DELIVERY stage.
At this point, we expand the project team by adding key specialists, typically including:
2-3 Backend developers (Python)
2-3 Frontend developers (JavaScript) – for web applications
2-3 Flutter developers – for mobile applications
DevOps Engineer
QA Engineer
UI/UX Designer
Additional specialists, such as Solidity developers, may also be involved depending on the project’s technical requirements.
With a team of 10-14 experts, development progresses steadily, sprint by sprint, as the product takes shape and moves closer to completion.
If the Discovery phase was properly executed and no unexpected changes arise, we are highly likely to stay within budget and timeline—something that is rare in the industry.
SUPPORT Phase
Once the core development is complete and the MVP is launched, we transition into support and ongoing improvements.
For minor refinements and optimizations, we usually keep a small support team engaged with a partial (25%) involvement, including:
Project Manager
QA Engineer
Backend Developer
Frontend or Flutter Developer
DevOps Engineer
If significant updates or new features are planned, the team can be scaled up accordingly.
If specified in the contract, our specialists can also prepare user documentation and provide training for the client’s team on how to use the product effectively.
If the client decides to discontinue support, we handover the source code after final settlements and reassign the team to other projects.
Should the client request future modifications, we would need to reassemble the development team. However, this is only practical for major updates requiring 500+ development hours.
Telegram 
WhatsApp 
