Software that does what you actually meant.
Between what you meant and what you get, every handoff loses context. lossless is built with fewer handoffs: small teams of senior engineers who hold context from the first conversation to production.
§01 · The idea
Software has a generation-loss problem.
The usual delivery model is a relay. What you meant becomes what the document says, becomes what the ticket says, becomes what got built, becomes what you got. Every step is another person with less context than the last. By the end, the product is technically complete and quietly missing the point.
Audio engineers call this generation loss: every re-encoding throws away a little more of the original. Nobody decides to lose the point. It falls out between people.
lossless is built to stop that loss. The team stays small and senior, the same engineers hold context the whole way, and every decision goes into a written record, so nothing depends on somebody remembering. The name is a claim you can test on the day it goes live: did what you meant survive the trip?
We work best with anyone who has watched a good idea come back as something else.
§02 · Principles
Three properties of lossless compression, applied.
Each principle comes from a real property of the format. That keeps them honest, and different from the three values every studio lists.
Intent survives the trip
The person who heard the problem is the person who builds the product. Every handoff is a place where meaning leaks out, so there are as few handoffs as the work allows.
You can always get the original back
Lossless compression is reversible by definition, and so is working with us. You get the full source and the written decisions, and the infrastructure runs in accounts you own. Leaving is a Tuesday, not a project.
Smaller is the craft
We aim for less code, fewer people, and a shorter path. The achievement is what we didn't have to build.
§03 · How we work
Four claims you can check yourself.
You get a working build every week and a written record of every decision we made and why. The rest of the model is four commitments. You can check each one in the first week.
You talk to whoever is writing the code
There is no account manager and no delivery lead relaying notes between rooms. Questions go straight to the person whose cursor is in the file.
Every decision, written down
The Manifest is a running log of what we chose, what we rejected, and why, written as the decisions happen. Six months from now, nothing depends on anyone's memory.
Your accounts, from day one
Infrastructure and domains live in accounts you own from day one. There is no handover at the end, because neither ever lived in our accounts.
Nothing only we can run
We build with standard tools and boring infrastructure, and nothing in the stack is proprietary. If we stopped tomorrow, the next engineer would read the Manifest and keep going.
§04 · Engagements
Four ways to hire us.
Each engagement is fixed-price with a written output, and each one stands alone. Pick the one that matches what you have.
Soundcheck
One week before anything gets built, to find the problems while they are cheap. We work out what the product has to do, what can wait, and what the smallest version worth launching looks like. You leave with the plan, a fixed quote for the whole build, and the first pages of your Manifest. When the right answer is to buy instead of build, the plan names the product.
Release
The product gets built by a small senior team: a working build to click through every week, every decision in the Manifest, and direct access to the people writing the code. When the plan and the date disagree, you hear it early, with what we'd cut. The engagement ends with a release you own and the record of how it was made.
Checksum
A fixed-price audit of your codebase, architecture, and infrastructure. It answers one question: does what you have match what you think you have? You get a map of the system as it runs today, every risk ranked by the cost of fixing it now versus later, and a starter Manifest. If the codebase is in good shape, the report says so.
Sustain
A flat monthly fee that keeps a live system healthy and its record current. Dependencies stay patched, small fixes go out as they come up, and every change lands in the Manifest. The engineer who answers your email is the engineer who knows the system.
The number you get before we start is the number on the invoice.
§05 · Contact
Tell us what you're building.
Write a few paragraphs about what you're building and what's gone wrong so far. You'll get a reply within two business days, from the engineer who would do the work.
hello@losslesssoftware.comNo form, no scheduling link. If it turns into a call, it's with the same person who read your email.