Clear scope. A more useful estimate.
We price from a written scope, not from a guess.
NetOfficials does not publish price lists, because the right price depends on what is built, by whom and under which engagement model. We start with discovery and a written scope you approve, then base the estimate on that scope so you know what you are agreeing to.
- Starts with
- Discovery
- Priced from
- A written scope
- Engagement models
- 3
- Confirmed in the contract
- Your IP
From Brief to Estimate
Every project moves from a written scope to agreed review points, so you always know what is happening and what comes next.
Share Your Brief
Tell us what you want to build. A senior engineer reads it and replies with questions.
Questions answeredDiscovery
We work through goals, users, systems and constraints until the shape of the work is clear.
Shared understandingWritten Scope
What will be built, by which team and under which model is written down for your approval.
Scope you approveThe Estimate
The estimate is based on the approved scope, so each part can be traced to what it covers.
A traceable estimateAgree and Begin
Once you agree, a named delivery lead starts the work in sprints, with a demo each sprint.
Work begins
Six Things That Move the Number
We do not quote figures on this page. These are the factors every estimate is built from.
Scope and complexity
More features, user roles and screens mean more design, build and testing work.
Integrations
Each system the software must connect to adds work to build and verify.
Team shape
The roles you need and the size of the team change the effort involved.
Engagement model
Project delivery, a dedicated team and team extension are organised, and so estimated, differently.
Platforms
Web, iOS, Android or all three change how much has to be designed and tested.
How soon you need it
A tighter schedule can call for a larger team working in parallel.
A Written Scope or a Quick Quote?
A fast number is tempting. For anything beyond a small, well-understood job, an estimate built on a written scope is easier to trust and to compare.
A scope-based estimate is usually the better fit when
- The work touches several systems
- More than one team will use the result
- You want to compare partners fairly
- You need to explain the figure to others
| Consideration | Estimate from a written scope | Quick quote from a call |
|---|---|---|
| What the figure is based on | The approved scope | A short conversation |
| Surprises during the build | Fewer, because assumptions are written down | More likely, because assumptions stay unspoken |
| Handling change | Agreed in the written scope | Negotiated as it happens |
| Comparing partners | Like for like | Hard to compare |
| Effort before you decide | More up front | Very little |
What Helps Us Estimate Well
You do not need a finished specification. These points make the first reply more useful.
Your goal
What the software should achieve for your business.
Who will use it
The people and roles who will rely on it.
Existing systems
Anything it must connect to or replace.
Must-haves and nice-to-haves
What is essential for a first release and what can wait.
Your deadline
Any date the work has to meet, and why it matters.
Your budget range
If you have one, it helps us suggest an approach that fits.
Pricing: FAQs
Do you publish prices?
No. The right price depends on the scope, the team and the engagement model, so we estimate from a written scope rather than a price list.
How do I get an estimate?
Send us your brief. A senior engineer reads it and replies with questions and a suggested next step, and the estimate follows the written scope you approve.
What makes a project cost more or less?
The size and complexity of what is built, the integrations involved, the team you need, the engagement model and how quickly you need it.
Does the engagement model change the price?
It changes how the work is organised and so how it is estimated. Project delivery follows an agreed scope, a dedicated team follows the team you agree, and team extension follows the specialists and hours you agree.
What happens if the scope changes?
How changes are handled is agreed in the written scope, so both sides know the process before the build starts.
Will I own what you build?
Yes. IP assignment is confirmed in the contract before the build begins, and you receive the full source code and documentation.
Ask for an Estimate
Share a few details. A senior engineer reads every brief and replies with questions and a suggested next step.
- We review your briefAnd reply with questions
- We sign a mutual NDABefore you share the details
- You get a written scopeTeam, timeline and model, before any commitment