The Spec · Design and build, fixed price

Specified, built and tested. Fixed at 5,000 EUR.

One clearly defined outcome, designed, built and tested for a fixed 5,000 EUR. We assess it free first and tell you within two working days whether it fits. Then the scope goes in writing, and that written scope is what the price covers. No retainer, no day rate, and the accounts stay in your name.

Summary

What is a J Labs Spec engagement?

A J Labs Spec is a fixed-price engagement that specifies, builds and tests one clearly defined outcome, for 5,000 EUR. It starts with a free assessment: tell us what you want built, and within two working days we say whether it fits the Spec, fits with one part left out, or is a bespoke build. If it fits, we write the scope down, you agree it, and that written scope is what the price covers. Then we design, build, test and hand it over, with the accounts and licences in your name. Typical work: enquiry triage routed into a CRM, first-draft quotes built from your own price list, invoice fields read into one system, call notes written back to the right record, an assistant on one defined body of your documents, or two systems kept in step on a schedule. Delivery is fifteen working days from scope sign-off. Registered as Jacarenda Labs LLC in Wyoming, USA.

Why this exists

Most AI consulting fails before it ships.

Discovery without an artefact

Most AI consulting starts with a discovery call and ends with a slide deck. The deck describes the work but cannot be built from. Engineering picks it up, asks twelve questions, and the project starts again.

Vague acceptance criteria

"Use AI to improve our reporting" is not a brief. Without a concrete definition of done (inputs, outputs, edge cases, who validates), every sprint negotiates the goal. Budgets blow. Timelines slip. Trust evaporates.

Priced by the day

Open-ended day rates make the vendor richer the longer it takes, so nobody is paid to be fast or to say no. A fixed price agreed against a written scope puts that risk on us instead, which is where it belongs.

The methodology

Scope that survives contact with engineering.

Before anything is built we sit with the people who run the workflow today, the people who would use the output tomorrow, and whoever looks after the systems it has to touch. We watch the work. We trace the data. We argue about acceptance criteria until they are concrete enough to test.

That becomes the written scope you sign off: problem statement, acceptance criteria, system context, data sources, and what done looks like. Every line is sourced from a real conversation or a real artefact in your business, not from a generic playbook. It is written down because a fixed price only means something when both sides can point at what it covers.

Then we build it. The same people who argued about the acceptance criteria are the ones who have to meet them, which is the point: scoping and delivery answer to each other rather than to a handover. You get the outcome working, not a plan for it.

The assessment comes first, and it is free, because the work has to be the right shape before anyone commits. If it is not, we say so and tell you what would fit instead. We would rather lose the sale at that point than take work we would have to squeeze.

What you get

An artefact, not a deck.

A free assessment, before you pay

Tell us the outcome you want and which systems it touches. Within two working days you get one of three answers: it fits the Spec, it fits with one part left out and here is which, or it is a bespoke build and here is what that would take instead. You are not committed until you say go.

A written scope you agree first

Problem statement, acceptance criteria, the systems involved, and what done looks like. You agree it before work starts, and that written scope is exactly what the fixed price covers. Nothing is left to be argued about later.

The thing itself, built and tested

Not a plan to build it. The outcome designed, built, tested and working, delivered within fifteen working days of scope sign-off, with the accounts and licences in your name and no markup on them.

A handover, and no surprises

We walk you and your team through what was built and how it runs. If the work turns out larger than the agreed scope we stop, show you exactly what changed, and price the difference for you to decide on. We do not absorb it quietly and we do not invoice you by surprise.

Download

The AI Project Brief Template. Free.

The one-page brief a Spec produces: problem, trigger, owner, data sources, acceptance criteria and the cost question. For operations leads scoping a first AI project. Fill it in before you talk to any vendor, including us.

Single email · No automated sequence · Unsubscribe with one click

The engagement

Five steps. Fifteen working days.

  1. The assessment

    Tell us the outcome you want and which systems it has to touch. Within two working days you get one of three answers: it fits the Spec, it fits with one part left out and here is which, or it is a bespoke build and here is what that would take instead. Free, and you are not committed until you say go.

  2. The scope, in writing

    We meet the people who run the process and whoever looks after the systems it touches. We watch the work, trace the data, and write down the problem statement, the acceptance criteria and what done looks like. You agree it before anything is built, and that written scope is what the fixed price covers.

  3. Design and build

    We build the thing. You get a short check-in as it comes together rather than silence followed by a reveal, so anything we read wrong is caught while it is cheap to change.

  4. Tested against what you agreed

    We test it against the acceptance criteria in the written scope, not against our own impression of what you wanted. That is the whole reason the criteria get argued over at the start.

  5. Handover

    Delivered within fifteen working days of scope sign-off. We walk you and your team through what was built and how it runs, and the accounts and licences stay in your name, paid direct with no markup. If you want it looked after afterwards, that is a separate conversation and not a condition of anything.

Frequently asked

Honest answers up front.