Skip to main content

Work together / The practical details

Start with the problem, not a proposal.

A webhook that keeps failing. An internal tool nobody trusts. A website ready for its next release. Show us what is happening and what needs to change. We will work out whether the right first move is a technical review, a focused build or support for an existing system.

Direct engineering. A written scope. A handover you can use.

01 / Engagements

Different jobs need different starts.

No compulsory discovery phase and no one-size-fits-all package. The shape of the work follows the risk, the current system and the decision you need to make.

01Technical review

Find the real constraint.

Useful when a build, integration or automation is stuck and the cause is not yet clear. We inspect the current flow before recommending changes.

  • Current-state and failure-path review
  • Prioritized findings and implementation options
  • Written next steps you can use with any team

Best for: diagnosing before committing to a rebuild.

Discuss a review
02Defined delivery

Ship a specific outcome.

For a clear website, app, API integration, MCP tool or automation milestone. We write down what is included and how acceptance will work.

  • Scope, assumptions and exclusions in writing
  • Implementation with meaningful verification
  • Deployment notes, documentation and handover

Best for: a bounded build or a meaningful first release.

Discuss a build
03Existing-system support

Make what's running dependable.

When the system already exists but needs fixes, evaluation, performance work or a safer operational path. We agree on the work before changing anything.

  • Bounded investigation or improvement backlog
  • Targeted changes with regression checks
  • Clear ownership of follow-up work

Best for: maintaining momentum without starting over.

Discuss improvements

02 / From first note to handover

A clear working sequence.

You can start with an imperfect brief. We make the unknowns explicit before they become expensive surprises.

  1. 01

    Show the current state

    Tell us what the system does today, who relies on it and where it goes wrong. Links, screenshots and error examples help; credentials do not belong in the first message.

  2. 02

    Choose the smallest useful scope

    We identify dependencies, access needs and acceptance criteria, then agree on deliverables, exclusions and a realistic estimate before work starts.

  3. 03

    Build, review, adjust

    Implementation stays inspectable. We check normal flows and failure paths, share tradeoffs early and agree on any scope change rather than silently expanding it.

  4. 04

    Hand over what matters

    You receive the agreed code or configuration, test results and practical operating notes. If ongoing help makes sense, we scope it separately.

03 / What stays with you

The handover is part of the build.

You should not need the original developer on the phone to understand what was shipped.

Access with boundaries

Credentials and permissions are handled deliberately. We request only the access needed for the agreed work.

Failures made visible

Retries, edge cases and recovery paths are considered alongside the happy path—not after the first incident.

A system you can operate

Source, configuration, decisions and runbooks are documented as appropriate to the engagement and agreed ownership.

05 / Before you get in touch

A few practical answers.

Do I need a complete technical specification?

No. A description of what is happening, what you want instead and what software is involved is enough to start. If requirements are uncertain, that becomes the first task—not an assumption hidden in the quote.

Do you publish hourly rates or fixed packages?

We estimate once the scope and dependencies are understood. A narrowly defined deliverable can suit a fixed scope; uncertain repair or investigative work may need a smaller initial assessment. Costs and milestones are agreed before work starts.

Can you work with an existing team or codebase?

Yes, when the access, responsibilities and constraints are clear. A focused review or well-bounded change is often better than a full rebuild.

What about support after delivery?

The handover is included in the agreed scope. Monitoring, maintenance or further development can be discussed separately; it is never implied as an unlimited commitment.

Next step

Tell us where the friction is.

Three details make a useful first message: the system involved, what happens today, and what you want to happen instead. We can take it from there.

Send a briefBrowse services

Please do not include passwords, API keys or confidential customer records in an initial enquiry.