Skip to main content
nimbryx

Process

How a project actually moves, start to finish.

No black box where your project disappears for three weeks and reappears looking nothing like what you asked for. Here’s the actual sequence.

Tell us what you're buildingSee the five steps
  1. 1Scope, honestly
  2. 2A real estimate
  3. 3Build in visible stages
  4. 4Test before it matters
  5. 5Launch, then stay reachable

Fixed price, in writing

Preview after every sprint

Five steps, in order

Each step ends with something you can see, read or use.

  1. Step 1

    Scope, honestly.

    1–3 days

    We ask what you're trying to solve, not just what you think you want built. Sometimes those are different things, and it's cheaper to find that out in week one than month three.

    • 30-minute call to understand the problem at a high level
    • We dig into your current workflow: what works, what breaks, what's still manual when it shouldn't be
    • We identify risks and ambiguities before they become problems
    • If we think you need something different from what you've described, we'll say so

  2. Step 2

    A real estimate.

    2–5 days

    Timeline and cost, in writing, before anything starts. If the honest number is higher than you expected, we'll explain why now instead of padding it later.

    • Detailed written proposal with fixed price and fixed timeline
    • Scope spelled out, including what's not in it
    • Payment schedule outlined (typically 40% to start, 40% mid-project, 20% on delivery)
    • No hourly billing. You know the total before you commit

    Typical payment schedule

  3. Step 3

    Build in visible stages.

    Project timeline

    You see progress regularly, not a single reveal at the end. Feedback happens while it's still cheap to change something.

    • Work is broken into 1–2 week sprints
    • You get a working preview link after each sprint, not just screenshots
    • A short weekly update on what got done, what's next, and anything we need from you
    • Feedback incorporated before moving to the next stage

  4. Step 4

    Test before it matters.

    1–2 weeks before launch

    We test against how the system will really be used, not just the happy path. The odd cases your business hits every week get tested too.

    • Staging environment that mirrors production
    • User acceptance testing, where you and your team use it before it goes live
    • Performance testing under realistic load
    • Cross-device and cross-browser testing for anything user-facing

  5. Step 5

    Launch, then stay reachable.

    Ongoing

    We hand off documentation, not just a login. And we don't disappear the day after go-live.

    • Deployed to your own server or cloud account. You own all of it
    • Admin and user documentation handed off at launch
    • 30-day post-launch support included in every project
    • Maintenance retainer available if you want ongoing support beyond that

Why trust a small team

Because the people scoping your project are the same people building it. There’s no relationship manager translating your concerns to a developer you’ll never meet, no junior team quietly inheriting the project once the senior person who pitched you moves on to the next deal.

We’re small enough that your project has a name to us, not a ticket number. That’s the real reason replies stay quick and things don’t get lost between people.

  • Response time to messages

    Same day or next morning

  • Status updates

    Weekly, without you having to ask

  • Access to your work-in-progress

    Staging link after every sprint

  • Post-launch support (included)

    30 days minimum

  • Who you talk to

    The person building it

Process FAQ

Questions we get before projects start.

How long does a typical project take?

A 5–8 page marketing website typically takes 3–5 weeks. A client portal or booking system is 6–10 weeks. A full custom software build (CRM, inventory system, etc.) is usually 10–18 weeks. These ranges assume feedback comes back within a few days. If reviews sit for weeks, the timeline moves with them.

What do I need to provide to start a project?

A clear description of the problem you're solving, access to any existing systems or data we need to integrate with, and a point of contact who can answer domain questions and give feedback during the build. We handle the rest.

How do you handle changes mid-project?

Small clarifications within the agreed scope are handled as part of the project. Bigger changes, like a new feature or a fresh integration, get their own written change order showing the extra cost and time. Nothing changes without your sign-off.

What if I'm not happy with the work?

We build in review stages specifically to catch issues early. If something isn't right, we fix it, and that's part of the price. If the final delivery doesn't match the agreed scope, we make it right. We've never had a project end in a dispute, and we'd much rather sort out a concern the day it comes up than argue about it after handoff.

Do you sign NDAs?

Yes. We're happy to sign a mutual NDA before any detailed discussion of your project. Ours is short and fair, the kind you can read in five minutes without calling a lawyer. If you'd rather use your own, that's usually fine too.

Who owns the code at the end?

You do, fully, upon final payment. You get the full codebase, access to all repositories, and complete ownership. We retain the right to list the project in our portfolio (anonymised if you prefer), but we have no claim to the work product itself.

Ready to start? We respond within one business day.

The first conversation is free and commits you to nothing. By the end of it you’ll know whether we’re the right team for this.

Tell us what you're buildingSee all services
  • Free first call
  • Fixed written estimate
  • 30 days of support after launch