SEGFAULTSEC
Services / Custom build

Built from the
request path up.

A product, not a prototype that has to be thrown away later.
A codebase you own, a team that answers, and something working in front of users early.

See how it runs
First working version 2–3 weeksYou own the code from day one
01 / who this is for

When the thing
does not exist yet.

Rebuilds fix what you have. This is for what you do not have: an internal tool, a product, the system your business actually runs on.

01Internal toolsThe dashboard, admin panel or automation your team currently does by hand in a spreadsheet at the end of every week.
02A product's first versionBuilt so the second version is an extension of it, not a rewrite. Most agency MVPs are thrown away. This one should not be.
03The system behind the businessOrders, clients, invoices, files, permissions. Unglamorous software that has to be correct every single day.
02 / what you actually get

Software that keeps
behaving.

You should not have to judge our tools. Judge these instead, because these are the things you will feel every week for years.

01It stays upBackups that get restored and tested, alerts that reach a person, and a way to undo a bad release in minutes. Most outages are not bad luck, they are missing preparation.
02It stays fastSpeed is designed in, not added at the end. We measure it on a mid-range phone on mobile data, and we give you the number before and after.
03It stays safeWho can see what is decided in one place, checked, and reviewed before launch. Security is part of every week, not a service you buy later.
04It stays yoursOrdinary, well-known technology that any competent team can pick up. No clever trick that ties you to us, and a written guide so nobody has to guess.

Want the technical detail? Ask and we will send it, or hand it straight to your developer. We just do not think it belongs on a sales page.

03 / how it runs

You see it working
early.

No three months of silence followed by a reveal. Something real is in your hands in the first weeks, and it grows from there.

Week 0

Scope and a fixed number

We write down what the first version does and, just as importantly, what it does not. You get a fixed price for that scope before any code exists. If we cannot scope it honestly, we say so instead of guessing at your expense.

Week 1

The spine

Database, authentication, deployment and the first real screen. From this week onward there is a URL you can open, and it is never broken for more than a few hours.

Weeks 2–3

The first version you can use

The core path works end to end. You use it with real data, not a demo, and what you find changes what we build next. This is where most of the important decisions actually get made.

Then

Weekly, until it is done

Every week you get a deploy and a short written note: what shipped, what we learned, what is next. No status meeting required, though we are happy to have one.

Handover

The keys, properly

Repository, database, deployment scripts, environment variables and a written runbook. Then a session with whoever will maintain it. You can walk away from us the day after launch and everything still works.

04 / what it costs

Priced by scope,
not by the hour.

Hourly billing pays us to be slow. We would rather agree a number, hit it, and have you come back.

Launch offer · 10% off every price

Internal tool

One team, one workflow, replacing a spreadsheet or a manual process.

from $13,410, 10% off $14,900
Typically 3–5 weeks
  • Authentication and roles
  • The core workflow, end to end
  • Database, migrations and backups
  • Deployed and monitored
  • Handover and runbook
  • No public sign-up or billing
Most chosen

Product v1

A real product with users who sign up, pay, and expect it to work.

from $26,100, 10% off $29,000
Typically 8–12 weeks
  • Everything in Internal tool
  • Public sign-up, plans and payments
  • Multi-tenant from day one
  • Admin panel for your team
  • Security review before launch
  • 30 days of support after launch

Ongoing

A system that keeps growing after the first version ships.

Custom
Monthly, scoped with you
  • An agreed share of our week, every week
  • You set the priorities
  • Hosting and monitoring included
  • Security review each quarter
  • Same engineers throughout
  • Cancel with 30 days notice

If the scope grows, we tell you the new number before we build it. You will never receive an invoice you have not already agreed to.

05 / honestly

When you should
not hire us.

We would rather turn work down than take it and disappoint you. Here is where we would tell you to spend the money somewhere else.

You want a bidding warIf the decision comes down to the lowest number, somebody will always go lower than us. We would rather you take that offer than resent ours.
You are still deciding what it isBuilding is expensive discovery. If the idea is not settled, a few weeks of talking to users will save you more than we can.
You want it in two weeksWe can ship something in two weeks. We cannot ship everything in two weeks, and we will not pretend otherwise to win the work.
06 / questions

The things people
actually ask.

Who actually writes the code?

We do. There is no account manager between you and the engineers, and nothing is passed to a cheaper team you never meet. You talk to the person who wrote the function you are asking about.

What if we want to take it in-house later?

Good. That is why the handover includes a runbook and a working local setup, and why we choose ordinary tools instead of clever ones. A new developer should be productive in a day, not a month.

Do you sign an NDA?

Yes, send yours before the first call if you prefer. We do not name clients or show work without written permission, and that stays true after the project ends.

What happens if the estimate was wrong?

If we underestimated our own work, that is our cost, not yours. If you change what you want, we quote the change and you decide. The line between those two is written down at the start so it is never an argument later.

Can you work with our existing team?

Yes. We review together, follow your conventions if you have them, and write ours down if you do not. We are not trying to be the only people who understand your system.

Where are you?

Morocco, working across European and North American hours. Everything is written down, so a time difference is a scheduling detail rather than a delay.

07 / start here

Send us a URL.
We'll tell you what hurts.

Building something new? Send whatever exists today, even a document. The free audit is how we start most conversations, and it costs you nothing.