Coherent Constructs

What we build

Available for work— taking new engagements

Coherent Constructs is a software studio. We design, build and repair the systems businesses run on — web applications, internal tools, and the integrations that hold them together. The people who scope your work are the people who write it.

How we price

We quote per engagement rather than per hour. You get a fixed figure and a written scope before anything starts, and if the scope changes we tell you what it costs before we do the work rather than afterwards.

Every engagement is quoted individually — get in touch and we will put numbers to it.

What I do

Product engineering

From a rough brief to something running in production.

We take a product from an initial brief through to a system your team can operate. That means the unglamorous parts as well as the interesting ones — schema design, deployment, error handling, and the tests that catch a regression before your customers do. We work in short increments with something demonstrable at the end of each, so you are never waiting on a big reveal.

  • A working, deployed application
  • Source code and infrastructure you own outright
  • Automated tests around the parts that matter
  • Documentation for running and extending it
  • A handover session with your team
Founders without an engineering teamBuilding alongside a full roadmapPrototypes that have outgrown themselves
Custom quoteContact for a quote

Typical turnaround: Typically 6–12 weeks, depending on scope

Talk to us about a build

Codebase rescue

For the system that works, mostly, and nobody wants to touch.

Software shipped under pressure accumulates a particular kind of debt: the parts everyone avoids. We work out what the system actually does, then make it safe to change again — characterisation tests first, then the refactor, in an order that keeps you shipping throughout. No rewrite unless a rewrite is genuinely cheaper, and we will tell you honestly which it is.

  • A written assessment of what is actually wrong, ranked by risk
  • Tests around the behaviour you cannot afford to break
  • Incremental refactors, each independently shippable
  • A maintenance plan your own team can carry on with
Releases that have quietly stalledSystems with no original authors leftWhen you have been told to rewrite
Custom quoteContact for a quote

Typical turnaround: From two weeks for an assessment

Tell us what is breaking

Architecture review

A second opinion before you commit.

A short, focused engagement answering one specific question: will this design hold. We read the code, talk to the people maintaining it, and come back with findings you can act on — what will break first, what will cost most to change later, and what is fine as it is. Useful before a funding round, a migration, or an acquisition.

  • A findings document, ranked by severity and effort
  • Specific remediation steps, not general advice
  • A walkthrough session with your team or your board
Technical due diligencePlanning a major migrationGetting an outside read
Custom quoteContact for a quote

Typical turnaround: One to two weeks

Arrange a review

How it works

  1. 01

    Conversation

    A call to understand the problem. No charge and no obligation. If we are not the right people for it, we will say so and point you somewhere better.

  2. 02

    Scope and quote

    We write down what we understand the work to be, what it will cost, and roughly how long it will take. You approve that before anything begins.

  3. 03

    Build in increments

    Short cycles, each ending in something you can actually look at. You see progress continuously instead of waiting for a reveal at the end.

  4. 04

    Handover

    Code, infrastructure and documentation are yours. We walk your team through all of it, and we stay reachable afterwards.

Questions

Who actually does the work?

The people who scope your work are the people who build it. Nothing is handed off to a bench you never met.

Do we own the code?

Yes, outright, including infrastructure definitions and documentation. We retain no licence over what we build for you, so there is nothing to unwind if you later take it in-house.

What happens if the scope changes?

It usually does. We re-quote the difference and get your approval before doing the work. You will not receive a surprise invoice.

Can you work alongside our existing team?

Often that is the best arrangement. We can embed with your engineers, act as an outside pair of eyes in review, or take a self-contained piece of work off their plate.

Tell us what you are building

A short description of the problem and roughly when you need it is enough to start. We answer every enquiry, including the ones we have to turn down.