Skip to content

How it works

How a NexaPrism project runs

You describe the engineering work, we agree the scope, timeline and price with you before anything starts, a lead engineer and senior team build it with a working demo every week, and we hand it over tested and documented. Here is each step in detail, what you get from it and what we need from you.

Send a project brief
  1. 01

    Brief

    You tell us what needs building or fixing.

    • Send a short brief through the form, email or WhatsApp, or book a free 15-minute call.
    • Tell us the problem, the system it touches, the stack and any deadline. A few lines is enough.
    • If you want a mutual NDA before sharing details, we sign it first.

    You get: A reply from a senior engineer within 2 business hours, with questions or a first view of the approach.

  2. 02

    Scope and quote

    We agree exactly what will be delivered, by when and for how much.

    • A senior engineer reviews the problem and, where needed, the existing code or architecture under NDA.
    • We write up the approach, deliverables, acceptance criteria, timeline, price and who will be on the project.
    • Larger or less certain work is split into phases, each scoped and quoted on its own.

    You get: A written proposal you can approve, change or decline. No work starts and nothing is billed until you agree.

  3. 03

    Kick-off

    Access, channels and working hours are set up.

    • You meet the lead engineer who will run the project.
    • Access is set up under your SSO with least-privilege permissions; we work in your repositories wherever possible.
    • We agree the channel (Slack, Teams or email), the weekly demo slot and the hours for calls in your time zone.

    You get: A named lead engineer, a shared channel and a fixed weekly demo in your calendar.

  4. 04

    Build, with a demo every week

    Senior engineers build it; you see working software every week.

    • Work lands as reviewable pull requests, with a short written update at the end of each week.
    • You have direct access to the engineers, not an account manager.
    • If you want to change the scope, we agree the impact on timeline and price with you before building it.

    You get: Working software to review every week, so there are no surprises at the end.

  5. 05

    Delivery and handover

    Tested, documented and walked through with your team.

    • Each deliverable is checked against the acceptance criteria agreed during scoping.
    • We hand over documentation, runbooks and a walkthrough so your team can own what was built.
    • Our access is removed. A next phase or ongoing support is scoped separately, only if you want it.

    You get: The finished work in your repositories, with everything your team needs to run it.

What you get at handover

  • Source code in your repositories, yours from the first commit
  • Automated tests for the critical paths
  • Documentation and runbooks
  • A recorded or live walkthrough for your team
  • A list of known limitations and suggested next steps

What we need from you

  • One person who can make decisions and attend the weekly demo
  • Access to the systems, repositories and environments the work touches
  • Feedback on each demo within a few days, so the build stays on track
  • Any constraints up front: security policies, compliance needs, deadlines

Questions about how we work

How long does scoping take?

It depends on the size of the work. A small, well-defined job can often be scoped from the brief and a call; a larger system may need a short technical review of the existing code first. Either way, you get a written proposal before any work starts.

Can the scope change during the project?

Yes. If you want to add or change something, we tell you the impact on timeline and price and agree it with you before building it. Nothing changes silently.

Do you work in our repositories?

Wherever possible, yes, under your accounts and access controls, so you can review every change as it happens. If that isn’t possible, everything is handed over in full at the end.

What if a deliverable doesn’t meet what we agreed?

Every deliverable is checked against the acceptance criteria written into the scope, and you see working software every week, so issues surface early and are fixed before handover.

Do you provide support after handover?

If you want it. Ongoing support, improvements or a next phase are scoped and quoted separately; nothing rolls into a retainer you didn’t ask for.

Working across time zones? See how calls and demos line up with your location, or read how pricing works.

Ready to describe your project?

Describe the problem. A senior engineer will tell you how we would approach it and roughly how long it should take: free, no obligation.

Send a project brief