CASRA Systems builds the website, backend, database, booking engine and AI operators that a service business runs on, as one system they own rather than nine tools they rent. Every sales call opens on a working concept of the client's own site, built before anyone speaks. See what we build.

You build the systems clients run their business on: the website, the booking engine, the customer and job database, the admin dashboard, and the integrations tying them to whatever software they already pay for.

The important constraint is ownership. Everything we build is handed over and owned by the client at the end, exportable, on their own infrastructure. That rules out clever things that only work while you are still around to maintain them.

What it pays

Not commission. Structure differs by engagement and is agreed in writing before you start, and it is the first thing we talk about on a call rather than the last.

What we are looking for

Something in production you can point at, and an honest account of what you would now build differently.
React and TypeScript at the front, Node and Postgres behind it. Adjacent stacks are fine if the work holds up.
Scar tissue from integrating against an API whose documentation lied.
You write the boring version first. Clever is a liability in a codebase somebody else inherits.
The ability to turn an owner's description of a problem into a schema without booking ten meetings.
No precious feelings about handover, including the parts you are not proud of.

Week to week

Build client systems end to end. No tickets off a backlog.
Model the data first, because the database is the part they keep.
Wire integrations to the tools the business already runs.
Write the handover: the client owns this after launch.
Fix what breaks in production on systems that are already live.

Not for you if

You want to work on one component of one product for a year.
You need a designer and a product manager between you and the requirement.
You have never shipped anything a stranger uses.

All open roles