Skip to content
Licence

We built the shop. You can run one too.

The pipeline that builds our work and the roles that run it, licensed under your own name. For the web shop, the freelancer or the IT firm that already has the clients and would rather deliver this than spend a year building it.

There is no tier, no badge and no directory. It is a licence to run the machine, and the machine is the entire product.

A flat monthlyA fee per project shippedNo share of what you charge
What is licensed

Six things,

and the sixth is the one that matters.

Anyone can copy the four scopes off this site in an afternoon. What takes a year is everything that stops a build going out wrong, and that is what most of this list is.

The build pipeline

Brief in one end, a live site out the other, with the same six stages our own work goes through.

Reads the brief, lays out the pages, writes the code, runs the checks, pushes to a preview link, waits for a yes. You decide which of those stops for a human, per client, the same way our clients do.

The six roles

Reception, Quotes, Invoices, Documents, Diary and the Monday report, ready to point at a client's accounts.

Each arrives with its brief, its refusals and the two-week watching phase already built in. You supply the client's price list and mailbox; the role does not need rebuilding per client.

The checks

The assertions that run on every push, which are most of the reason a week is enough.

Text contrast measured from rendered pixels, horizontal overflow at two widths, tap-target sizes, accessible names, dead links, the legal pages present, and the type scale unbroken. A build that fails one does not reach the preview link.

The four builds

Website, shop, bookings, internal tool — the scopes, the layouts and the drawn previews.

Including the parts that are boring and take a week to get right on your own: the checkout, the TWINT flow, the reminder mails, the cancellation rules, the export back out to Excel.

Your name on it

Your domain, your logo, your prices, your contract, your support address.

Nothing a client of yours receives says recursiv, including the preview links, the mails the roles send and the footer of the sites you ship. There is no powered-by line.

What we ship, you get

Same week, not a version behind.

We use this to run our own shop, so it is fixed because it broke for us, not because a roadmap said so. When a check gets stricter, it gets stricter for everyone at once.

Whether to buy it

The reasons not to,

before the reasons to.

A licence somebody cancels in month two costs them two months and costs us the support. Both lists below are written to be used, and the right-hand one is longer.

The same machine, another name on it
This is for you if
  • You already have clients, or a way of getting them
  • You can read a diff and say whether it is wrong
  • You want to sell builds without hiring to deliver them
  • You handle your own first line of support
This is not for you if
  • You are looking for a way to get clients — this delivers work, it does not find it
  • You want somebody to take the call when a client is angry
  • You have never shipped a site and want this to be the way you learn
  • You need it to say your name on the invoice but ours on the blame
Getting started

Three steps,

and one of them is us doing the work.

One project together, then you ship the next
01

One call

Half an hour on what you already sell and to whom. If the answer is that you do not need this, that is the answer you get.

02

One project, side by side

We ship a real build with you, on your infrastructure and under your name, before you have sold one. Included in the first month.

03

You ship the next one

We stay reachable in writing. The support you get is the support we would want: a person who has read the code, answering within the day.

How it is bought

A monthly, and a fee per project.

No share of your revenue.

The figures come in the reply, because what they should be depends on how many builds a year you would put through it. What does not depend on anything is the shape of the deal, and that is below.

A flat monthly

One licence fee, whoever you are and however big you get. No seat count to manage and no tier you fall out of the month you have a good quarter.

A fee per project shipped

Charged the day a build goes live rather than the day it starts. A project you scope and never ship costs you nothing.

No cap on projects

Put as many client builds through it as you can sell. Nothing throttles, and nothing renegotiates because the year went well.

A month's notice

Work you have already delivered keeps running whatever happens to the licence. Your clients never find out you stopped paying us.

We take no share of what you charge. What you bill your client is between you and your client, and we never see it.

What the quote depends on is what you already sell and how many builds a year you think you would put through it. Say both in the first mail and the figures come back in the reply.

Tell us what you already sell, and to whom.

Half an hour is enough to know whether this is worth either of our time. If the answer is that you do not need it, that is the answer you get — this is a licence, and a licence that gets cancelled in month two is worse than no licence at all.

Answered by somebody who has read the code, usually the same day.