Runset

How we work

Written scope first. Then the work.

Both lines of work run the same way. The scope exists so you can hold us to it, and so the two of us agree on what “done” looks like before anyone starts building.

The sequence

1.0

First call

What the job is, what the deadline is, and what the difficult part will be.

2.0

Written scope

Deliverables, dates, price, and what is explicitly not included. You approve it before we start.

3.0

Build

Short cycles with something to look at. Changes outside the scope get re-quoted, not absorbed silently.

4.0

Handoff

Accounts, credentials, documentation and a walkthrough. The work runs without us.

Settled before you ask.

The parts of an engagement that usually stay unsaid until something goes wrong. None of it is negotiated later, it’s how we work by default, on every project.

How we operate

ContractsScoped in writing before work startsno open retainers
ChangesRe-quoted, never absorbed quietlyyou approve first
OwnershipAccounts and credentials stay yoursincluding the automation
DeliveryThe people you talk to are the people building itshort feedback loop
HandoverDocumentation, code and a walkthroughyour team runs it

Start with the hard part.

Lead with the bit you think is impossible. It’s the part we most want to look at, and it’s usually where the interesting version of the project is hiding.

Start a project