Skip to content
ANB Codes

Strategy and design

Plan your idea and first version

A short, structured sprint before any code is written. We map the users, the must-have features and the risks, then hand you a clickable prototype, a technical plan and a fixed quote for the build.

Overview

Turn your idea into a clickable sample, a clear plan and a fixed price.

Most software projects that go wrong do so before a line of code is written. The scope is vague, suppliers price different things, and nobody can say what the first version must do. This service turns an idea into something concrete: a clear picture of who will use the product, what they need from it, and what it should cost to build.

Our first step is a workshop with the people who know the business best, to agree goals, users and what success looks like. From there we help you decide what belongs in version one and what can wait, and we flag the integrations and data that carry risk. Key screens are tested with real users before anyone commits to a build.

At the end you hold a clickable prototype, a scope document, a technical plan and a fixed quote with milestones, all in writing. Those documents are yours to keep and can be taken to any supplier. If you go ahead with us, the discovery fee is credited to the build, and the people who planned the product carry the work forward.

What you receive
Prototype link · Scope document · Architecture diagram · Roadmap · Fixed quote
Typical technology
Figma · Miro · Maze · Notion

Who it's for

Is this right for you?

If you already have a detailed specification and designs, skip this and ask for a fixed quote straight away.

  • A founder with an idea who needs a clear scope before paying for a build
  • A business comparing supplier quotes that don't line up
  • A team that must show investors or a board something they can click

Scope

What goes into it

Every engagement is scoped to your goal. These are the parts most projects include.

  • Stakeholder workshopsGoals, users, constraints and what success looks like.
  • User journeysThe key flows mapped screen by screen.
  • Clickable prototypeTested with real users before development.
  • Technical planArchitecture, integrations, hosting and risks.
  • Release roadmapWhat goes in version one, and what can wait.
  • Fixed quoteScope, milestones and timeline in writing.

Timeline

How a typical project runs

Usual length: usually 2 to 3 weeks. Your written scope gives the exact plan.

  1. 01Week 1

    Goals and users workshop

    We agree who will use it, what they need to do and what success looks like for you.

  2. 02Weeks 1–2

    Must-haves and risks

    We sort features into version one and later, and flag the integrations and data that carry risk.

  3. 03Weeks 2–3

    Clickable sample tested

    You click through the key screens, we test them with a few real users, then adjust.

  4. 04Week 3

    Plan and fixed quote

    You get the technical plan, release roadmap and a fixed quote with milestones, in writing.

One-time project

A fixed quote for an agreed scope, paid in milestones. You own the code and accounts once it's paid.

Monthly care plan

A monthly subscription that keeps your software secure, monitored and improving, with response times in writing.

Getting started

What happens after you get in touch

Discuss your project
  1. 01Tell us the problemA short form or a call. A senior lead replies within one working day.
  2. 02One callWe sign an NDA first if you need one, then go through your goals, users and current systems.
  3. 03Written scope and fixed quoteWithin 48 hours of the call, with milestones and a timeline.
  4. 04Build in milestonesYou see working software at every milestone, and you own what we build.

Questions

Before you ask

What changes the size of the job

  • How many types of user the product has, such as customers, staff and admins
  • How many outside systems it must connect to
  • How many user test sessions you want on the prototype
How long does discovery take?

Usually two to three weeks, depending on how many user groups and integrations are involved.

Do I have to build with you afterwards?

No. You own the prototype and the documents, and can take them to any team.

Is the discovery fee lost if we don't go ahead?

You keep everything we produce: the prototype, the scope and the quote. If you build with us, the discovery fee is credited to the build.

What do you need from us during discovery?

A few hours a week from the person who knows the business best, plus examples of the forms, spreadsheets or tools you use today.

How is this priced?

As a one-time project with a fixed quote, agreed after a short call and paid in milestones. After launch you can add a monthly care plan for hosting, updates and support.

Tell us what you need built.

Share the problem in a few lines. After one call you'll get a written scope and a fixed quote within 48 hours.