BRUTALLY HONEST · THE DISQUALIFICATION PAGE

If we’re wrong for you, we’d rather you know now.

Most studios hide their limits. We publish ours — because the worst client engagement is one that should never have started. Read this before you book a call. Especially the parts that disqualify us.

What we don’t do.

×
We don’t do enterprise sales cycles. If procurement needs 6 weeks and 4 stakeholders, we’re probably wrong for you. We’re built for founder-led decisions.
×
We don’t white-label. Our work ships with our fingerprints. If you need to claim it as your team’s, hire a freelancer instead.
×
We don’t do landing pages alone. If you don’t need an automation layer behind it, we’re overkill. Hire a designer.
×
We don’t take small retainers. Below our minimum cadence we can’t deliver our embed model — and bad embeds become bad outcomes. (Pricing on the call.)
×
We don’t work weekends except in launch weeks. Founders included. The work that needs weekends is a process problem.
×
We don’t do RFPs. Beyond a 1-pager scope. If you need a 30-page response, you’re probably solving a different problem than software.

Who we say no to.

×
People who lead with “we’re going to disrupt X”. If your first paragraph isn’t about a specific painful workflow, we can’t help.
×
People who don’t pick up their own customer calls. If you’re too senior to talk to your users, you’re too senior to brief us.
×
People who treat us as agencies. We’re a studio. We co-build, we don’t take orders. If you want a vendor, we know good ones.
×
Crypto, gambling, predatory lending. We’ve passed on serious money in these. Not changing.

When we screw up.

We're pre-customer — so we don't have a client-screwup receipt to publish, and we won't fake one. What we can tell you is how we've handled the misses on our own builds, and the rule we'll hold ourselves to once you're on the line.

OUR BUILDS

We underestimate edge cases — and then over-deliver to fix them.

On our own projects, the thing that bites is always the integration edge case we didn't scope. We've learned to ship the working core first and absorb the overrun ourselves rather than pass it on.

DATA

We've lost data in a migration — on our own systems.

It's why the WhatsApp bot we built has backup hooks, WAL-safe snapshots, and a one-file restore baked in from the start. We'd rather over-engineer recovery than learn the lesson on your data.

THE PROMISE

If we miss with you, you'll hear it from us first.

No customer has caught us out yet because there's no customer yet. When there is, the rule is simple: we tell you before you notice, we eat the cost of our miss, and the 14-day promise means you're never on the hook for a build that isn't right.

IF YOU READ ALL THIS

You probably are the right kind of person to work with.

The people who skip this page tend to be the ones who later say we should have warned them. So we did. Now you decide.

WhatsApp us anyway →