Loading…
Loading…
The rest of this site is written for founders, and the booking flow is shaped for them. If you are evaluating a contractor on behalf of an engineering organisation, this page and the two it links to are the ones worth your time — they answer what your security, legal and finance functions are going to ask, before anyone has to ask it.
Work is quoted and delivered as a statement of work against a named outcome. An hourly figure is supplied where your intake form requires one, but the engagement is governed by the scope — which is the document both sides actually want to be arguing about if something changes.
No standing production credentials, read-only where read-only is enough, and no client data copied onto local machines. Access is enumerated before work starts so it can be reviewed and revoked as one list — which is also what keeps a vendor-risk review proportionate.
There is no bench behind this, no account manager, and no handoff to someone you have not spoken to. That is a real constraint on capacity and a real advantage on everything else, and the continuity answer is published rather than promised in a call.
Two URLs your champion can paste into a thread. Both are dated with the day somebody last checked their contents were still true, because an undated trust page is a claim with no expiry.
An exhaustive subprocessor list with what each one can see, the controls that are implemented with the file that implements them, and an explicit statement of what is not held — including the absence of a SOC 2 report and why buying one speculatively is the wrong trade at this size.
ProcurementW-8BEN and reverse-charge handling, purchase-order process, payment rails and realistic timelines, the key-person substitution answer, and a plain statement of the two things that are currently open — insurance and entity.
Proof of outcomes beats description of process, and this section is written to be honest about which of those it currently has.
No client case studies are published yet. Rather than fill the space with generic claims, here is what can actually be inspected: this site is a production Cloudflare Worker running Next.js, Prisma against D1, Stripe with 3-D Secure and an append-only payment ledger, and a live MCP server whose tool manifest is contract-tested in CI so a capability cannot ship undeclared.
The controls listed on /security each name the file that implements them. That is a weaker form of evidence than a client outcome and a stronger one than a testimonial, and it is the form that is currently true.
The booking wizard verifies a card to deter no-shows, which is fine for a founder and is a policy question inside a larger company. So it is not the only door.
A video call to scope the work. The booking step verifies a card without charging it, which exists to deter no-shows and nothing else — if that is a problem inside your organisation, use the form instead and a time gets arranged by email.
Bring whoever else needs to be in the room. The slot is 30 minutes for one person or for four.
Every packaged engagement on this site carries its floor in public, and a quote for scoped work never comes in under the number that was advertised. Transparent pricing is the most consistent thing buyers ask vendors for and the most consistent thing they do not get.