Tomoe · service 06

Someone built it.
Then they stopped
answering.

You have a system that runs your business and nobody who understands it. Every quote you get is either "rebuild everything" or a silence. There is a third answer, and it starts with reading the code.

Send us the repo

five layers · the stack opens on its own

The five layers we read

  1. 01Interfacewhat the user touches
  2. 02APIwhat the browser is allowed to ask for
  3. 03Business logicwhere the rules actually live
  4. 04Datathe schema, and what it lets through
  5. 05Infrastructuredeploys, backups, domains, keys

read worth a look needs fixing — illustrative. Those are the surfaces we open, not findings from your system.

audit.diffillustrative
-if (user.role == "admin") { /* client-side only */ }
+requireRole(req, "admin") // checked on the server
-const price = req.body.price
+const price = await catalog.priceOf(req.body.sku)
-// TODO: verify signature
+verifyWebhook(req.rawBody, req.headers["x-signature"])
01

We read it

Two to three days with the code, the database and whatever docs exist. No meetings needed from your side.

02

You get the truth

What works, what is fragile, what is dangerous, and what it would cost to keep versus replace. In writing, in plain language.

03

You decide

Carry it forward, rebuild the risky parts, or start clean. Sometimes the honest answer is the one that earns us less.

04

We take the keys

Deploys, backups, domains, and the phone number that gets called when it breaks at 9pm.

What we will not do

We will not tell you it is all garbage so we can quote a rebuild. If the previous developer did decent work, you will hear that — and the job gets smaller and cheaper. That is the whole point of asking someone who is not trying to sell you a rewrite.

Now taking work

Send us the repo
Services