How working with us actually goes

Workflows explain how we would build your kind of thing. This page explains what it is like to work with us: the contracts, the communication, the ownership, and the handover.

Three ways to work with us

Every engagement is one of these three. The scope call ends with a recommendation and the reason for it.

Fixed scope

Defined deliverables, a fixed price, and a fixed timeline. If we estimated wrong, that is our problem.

Choose this when the requirements are clear.

Dedicated team

Engineers assigned to you full-time on a monthly basis, with a milestone plan that changes in writing.

Choose this when the work is ongoing or the scope will evolve.

Staff augmentation

Individual senior engineers joining your team and your process, in your tools and your standups.

Choose this when you have a team and need a specific capability.

Delivery, in six steps

What happens and how long it takes, from your first message to the handover.

  1. Enquiry and call

    Within one business day

    You tell us what you are building. An engineer replies with a few questions or a time for a call. No deck required.

  2. Scope and proposal

    One to two weeks

    A short discovery ends in a written scope: what is in, what is out, the engagement model, the price, and the date.

  3. Contract and kickoff

    A few days

    Repositories, channels, and accounts set up in your name. The first demo is booked before the first commit.

  4. Build in weekly cycles

    The bulk of the engagement

    A demo on staging every week, a written summary every Friday, and a backlog you can see and reprioritise.

  5. Launch

    Planned, reversible

    Production deployment with monitoring, a rollback ready, and the handover documentation already written.

  6. Support and handover

    30 days included

    Fixes on anything we built, then a maintenance retainer or your team taking the controls with the runbooks.

Communication

  • A shared Slack or Teams channel with the engineers on your project.
  • A weekly demo on a live staging environment you can use any day.
  • A written summary every Friday: what shipped, what is next, what we need.
  • Calls in your timezone, not ours.

Tooling

  • Your repositories, or ours transferred to you at launch.
  • Your project tracker, or ours, with the same backlog either way.
  • Your cloud accounts wherever possible, so the bills and access stay in your name.

What you own

Source code, repository history, infrastructure configuration, documentation, designs, and all intellectual property. Transferred at launch, and available at any point before it. It is in the contract, not on a slide.

After launch

The support window

Anything we built that breaks in the first 30 days after launch is fixed at no charge.

A maintenance retainer

Updates, patches, monitoring, and small changes for a monthly fee, with the same engineers.

Taking it in-house

Handover sessions with your engineers, the runbooks, and our availability for questions. Nothing is locked to us.

Tell us what you are building.

We reply within one business day with how we would build it, what it would cost, and which engagement model fits.

Start a projectnadirhussaint03000@gmail.com
  1. 01
    Tell us what you are building

    A short form or an email. No deck required, and "not sure yet" is a fine answer.

  2. 02
    A call with an engineer

    Within one business day. Technical questions get technical answers, from the person who would build it.

  3. 03
    A written scope and quote

    Fixed price where the scope is defined. The document is yours whether or not you go ahead.