Quick start · Applications · 2 weeks

Product scoping. Two weeks to a fixed cost you can sign.

Q: How fixed is the fixed cost?

Fixed for the scope as written. The assumptions are listed. If the scope changes, the change is priced before it is built, never absorbed and never a surprise invoice.

Q: Do we need to know the technology?

No. We recommend the stack based on what it must do, what you already run and who will maintain it, and explain the choice in plain terms.

Q: What if the honest answer is that it should not be built?

Then that is the answer you get. Sometimes a workflow in an existing platform does the job. The scoping says so, and costs the same.

Before an app or a platform is built, the brief is turned into something a team can price and a board can approve: user flows, screens, data model, integrations, the build plan and a fixed cost with a date.

If you then build with anyone else, the scope is still yours and still usable.

Start the product scoping All quick starts

Length: 10 business days, two workshops included.
You get: Flows, wireframes, architecture, plan, fixed cost.
Cost: Fixed, agreed in writing before we start.
Clients rate us: 4.7 / 5 from 23 Google reviews

Who does what

You bring the problem. We bring the plan.

You hold

The people who know the business problem, for two workshops
Any existing documents, screens or systems it must talk to
A decision maker on the final call

Codeeo holds

User flows and a screen map for every role
Clickable wireframes of the main journeys
Architecture, data model and integration list
A phased build plan with a fixed cost and dates

What you walk away with

A scope a team can build from, not a brief.

User flows and screen map: Every role, every journey, every screen named, so nothing is discovered in month three.
Wireframes of the core journeys: Clickable, low fidelity, enough to test with real users before design starts.
Architecture and data model: What runs where, what talks to what, and which existing systems are integrated rather than replaced.
The build plan: Phases, what ships in each, the team on it and the dependencies on your side.
Fixed cost and timeline: A number and a date in writing, with the assumptions listed so changes are priced, not absorbed.

How the two weeks run

Two workshops, one plan.

Every quick start runs on the same rule: a written scope and a fixed cost before day one, a named lead, and a report you own whether or not you continue with us.

Week 1: discovery
Workshop one, interviews with the people who will use it, a review of the systems it must connect to.
Week 1: flows and screens
User flows drafted and reviewed with you mid week, screen map agreed.
Week 2: wireframes and architecture
Wireframes of the main journeys, data model and integration design.
Week 2: plan and cost
Workshop two to walk the plan, then the fixed cost and timeline in writing.

Is this the right start?

Is product scoping the right start?

You have a brief or an idea and need a number you can take to a board or an investor.
Quotes you have received vary wildly and you do not know why.
The product must integrate with systems you already run.
You want to test the journeys with users before paying for design.

0/4

Tick what describes you

The verdict updates as you go. Nothing is recorded.

Or, if you

The site exists and just needs fixing.Start with a website audit
You are choosing between Dynamics 365, Odoo or another platform.See the platform fit review
You have a codebase and want to know its state.See the codebase review

Questions about the product scoping

Is the scope usable with another agency?

Yes, and it is written that way.

Flows, wireframes, architecture and the plan are yours. Any competent team can build from them.

How fixed is the fixed cost?

Do we need to know the technology?

What if the honest answer is that it should not be built?

Other quick starts

Not the right question? There are eight more.

All quick starts

Start it

Start the product scoping.

A reply within one business day with the scope and the fixed cost in writing.

1
A reply within one business day
From the lead who would run it, with two or three questions.
2
The scope and cost in writing
What is in, what is out, the fixed cost and the start date.
3
Access and start
Read only access on your accounts, and the work begins.

First nameLast name

Work emailCompany

Country or market

Phone

Which quick startHow did you find us

What prompted thisI agree to Codeeo storing these details to reply to this request.