About
VERA Technologies is a two-person software studio in Orange County, California. We design, build, ship and then operate the things we make — which is a different job from building them and handing them over.
Who we are
Two of us, and that is deliberate rather than a stage we are trying to grow out of. Two people can hold an entire system in their heads at once. Nothing gets built because a handover document was ambiguous, and there is no layer of people between the person who decides and the person who types.
When a job genuinely needs more hands, we bring in developers we have worked with and trust, for that piece of work. They are briefed, reviewed and paid by us — you deal with the two of us either way, and the accountability does not move. We would rather widen the bench for a month than pretend two people can do everything at once, and we would rather tell you which of those is happening than quietly staff up and bill you for the learning curve.
How we work
One project at a time, scoped in writing before anything is built. We would rather spend the first week telling you what something will cost to run than the last week explaining why it costs that. Estimates come with the infrastructure bill attached, because we are the people who pay it on our own products and we know what the line items actually are.
We work AI-assisted, inside gates we wrote. What that means concretely — including where it stops helping — is on the method page rather than buried in a paragraph here.
Working together
The first deliverable is always the brief, and you approve it before anything gets built. It names what you want to be true when this is finished, who it is for, what must not be claimed, and what the ongoing effort can realistically be — because a scope nobody has written down is a scope nobody can be held to, and it is where most of the money gets lost.
After that you see work in progress rather than a reveal at the end, and anything with a budget attached stops and waits for you. That is not a policy we retrofitted: the ad tooling we build creates every campaign paused, so nothing can start spending without a person deciding it should. You can read the six requirements one of these briefs actually contained on the OC Design 949 page — the whole case study is organised as a response to them.
What we will not do
We will not quote a fixed price on a scope nobody has written down. We will help you write it down, and we will quote that. We will not take on work that needs twenty engineers and a dedicated project manager from day one, and we will say so on the first call rather than the third.
Where things stand
Two businesses are live, and we run both at full engagement scope.kudo.kids is on the App Store — product design through to the cloud bill. OC Design 949 went from a positioning problem to a brand, a live site, a publishing pipeline and an ad campaign.
We own both, so no invoice changed hands on either. We would rather tell you that than have you find it out: everything else about them is the same work, at the same scope, that we would do for you — and because we own them, we are still the ones paying the bills and answering for the decisions years later. That is a harder test than shipping something and walking away.
Getting in touch
Email is the only channel. There is no form, no chatbot and no booking link — if you want to talk about building something, a few sentences in an email gets there faster than any of them.