Intactic
Start a project

Engagements

Three ways to work together.

The shape of an engagement should follow the problem, not a sales target. These are the three we run, what each one is for, and what it asks of your team as well as your budget.

Platform build

A complete system, owned end to end.

3–6 months

For a new product, or a replacement of the thing that has become the constraint. We take it from discovery to the first month in production, then hand over a system your team can run.

What is included

  • Discovery, domain model and architecture
  • Interface design and a working design system
  • Engineering in two-week increments
  • Testing, accessibility and performance checks
  • Launch, migration and a support window
  • Documentation, runbooks and a recorded walkthrough

The shape

Team
3–6 people
Length
3–6 months
Billing
Milestones
Best for
New products, replacements

The most common first engagement, and the one where we carry the most risk. We price it accordingly and put a named lead on it.

Embedded team

Our people inside your product organisation.

Monthly

For a team that already has a roadmap and needs senior hands on it, without a procurement cycle for every decision. We join your rituals and work to your priorities.

What is included

  • One to four engineers or designers
  • Code review and architecture support
  • Release ownership, where you want it
  • A written update every week
  • Your board, your standup, your definition of done

The shape

Team
1–4 people
Length
Rolling, monthly
Billing
Monthly
Best for
Scaling delivery

We ask for a named technical owner on your side. Without one, embedded work quietly turns into consulting, which is a different service and a worse deal.

Assessment & augmentation

A short, fixed-scope look at what you run.

4–10 weeks

For a system in production that has become slow, expensive or difficult to change. We audit it, choose one improvement that pays for itself, and ship it.

What is included

  • Architecture and running-cost audit
  • Data quality and reconciliation review
  • One workflow shipped to production
  • An evaluation harness, where models are involved
  • A written recommendation and a costed roadmap

The shape

Team
2–3 people
Length
4–10 weeks
Billing
Fixed fee
Best for
Existing platforms

You keep the audit whether or not you continue with us. That is the point of doing it this way.

Money

How pricing works.

No hourly billing for thinking, and no quote before we have read the system.

Discovery

A fixed fee for one to two weeks. Credited against the build if you continue, so the work is not paid for twice.

Build

Milestone-based against a written scope. Three or four milestones, invoiced on acceptance rather than on effort.

Embedded

Monthly, with thirty days notice. Enough commitment to plan around, short enough that a stop is a decision rather than a project.

What we need

Engagements that work need both sides.

  • A decision-maker in the room, not on a mailing list
  • Access to the people who do the work today
  • A named technical contact for the build
  • Repositories and documentation, where they exist
  • Permission to cut scope that does not serve the goal

Contracts

Plain terms, in writing.

We sign your NDA and your master agreement, or provide ours. Work is governed by the contract we both sign, not by a proposal deck.

Deliverables, acceptance criteria and payment terms are stated in the same document. If a change is needed, we write a change note with the cost and the effect on the date before any work starts on it.

See how a build runs

Questions

Asked before contracts.

Something not covered here? Write to hello@intactic.net and you will get a direct answer.

Who owns the code and the infrastructure?
You do. Repositories, cloud accounts and keys are opened in your name from the first week. There is no licence fee to keep using what we built, and no dependency on our hosting.
What happens if the scope changes?
We write a change note: what is added, what it costs, what it does to the date. It needs your written approval before work starts. Scope that is removed is credited at the same rate.
Can you work alongside another agency?
Often. The arrangement works when the boundary is explicit: which system each team owns, how releases are coordinated, and who decides when the two disagree.
Do you take small projects?
Assessments start at four weeks, which is the smallest piece of work we can do properly. Below that, we are usually the wrong choice and will say so.

Next step

Tell us what you’re building.

Send a short brief. You get the questions that matter, a rough shape of the work and a straight answer on fit.

Start a projecthello@intactic.net

No sales sequence