How a quote comes together
This is the path for a fixed-scope project. For time & materials work, the single price in step three becomes an hourly plan instead.
- 01
Free scoping call
30 minWe talk through what you want to build, who will use it and what you already have. If you like, run the quote wizard first so you arrive with a rough scope and timeline.
- 02
Written scope
We write up what we discussed in terms of screens, user roles and integrations. The price is based on this document, so you can see in one place what it covers.
- 03
One total price
For fixed scope you get a single figure tied to the written scope. If the scope changes later, we send you the time and budget impact in writing within 24 hours.
- 04
30% up front
30% of the price is paid when work begins. You get one product owner as your single point of contact, and you can see the same task list we work from.
- 05
Delivery milestones
Weekly versionThe remainder is split across delivery milestones, with a working version at each one. Between milestones you still get a new working version every week.
Paying from abroad or in Turkish lira
Choosing between the four models
Two questions settle most of it: how clear your scope is, and how long the work will run. The table matches typical situations to a model.
| Your situation | Model | How you track the budget |
|---|---|---|
| You know what you need and the budget has to be fixed up front | Fixed scope | One total price in writing; any scope change comes with its impact in writing within 24 hours |
| The idea is clear, but the details will take shape with user feedback | Time & materials | Billed on hours worked; the open task list shows what those hours went on |
| A long-running product that needs steady development | Dedicated team | 2-6 engineers, billed monthly, minimum three months |
| A live system that needs upkeep and small improvements | Monthly retainer | A fixed monthly package |
You don’t have to stay with one model. You could build the first version on a fixed scope, for example, and move to a retainer or to time & materials afterwards.
Four ways to keep the cost down
These are general tips that hold whichever team you work with.
Start with an MVP
Put only the core flow in the first version and add the rest as feedback comes in from real users, so you don’t pay for features nobody uses. A typical first working version of a web app ships in 2-4 weeks.
Bring your design if you have one
Finished screen designs or an established brand guide save work, so share them at the start. Whether design starts from scratch is one of the things that moves the price.
Phase the integrations
Connect the one system the product can’t run without first, and leave the others for later phases. The first version ships sooner and costs less.
Keep one decision-maker
When one person signs things off, less time goes on waiting and on untangling conflicting feedback. On our side, you deal with a single product owner too.
What’s in the price and what isn’t
On a fixed-scope project the quoted price covers everything in the first list. The second list is third-party fees, which you pay directly to those providers.
Included in our price
- All source code, transferred to you with the IP on final payment
- Documentation and setup instructions at delivery
- A working version every week and an open task list you can see
- One product owner as your single point of contact
- 30 days of free bug fixes after launch
Paid to the provider
- Hosting and domain names
- App Store and Google Play developer accounts
- AI model usage
- Other paid third-party services, such as SMS, maps or payment processing