We Build iPhone and Web Apps Again

For fifteen years I built software. Quietly, mostly for people who already trusted me: iPhone apps and web apps that did one specific job and did it well. I never put it on the menu, because the practice was built around judgment. Give you an honest read on your technology, tell you the path I'd take, and stay in the room while it got built.

We've done enough of it now to put it back on the menu.

What we build

Native iPhone and iPad apps. Web applications. The internal tools a business actually runs on: approval workflows, forms systems, member and customer portals, and the integration that finally makes two systems you already pay for talk to each other.

Still blueprint first

None of the discipline changes. The architecture gets documented and pressure-tested before a line of code, and we build on the blueprint, not around it. What changes is this: when the answer is build, you no longer have to go find a shop and hope they understood the plan. The people who wrote the plan can build it, and stay accountable for it working.

Why bring it back now

AI changed what a small, senior team can ship. Work that used to take a floor of developers now takes a tight team that knows exactly what it's doing. That's the kind of team I've always run. You get custom software without the custom-software headcount, and an advisor who still owns the outcome.

If you have something that needs building

If you've been quoted a fortune for an app, or told your idea can't be done the way you want it, send me a note. I'll give it to you straight: build it, buy it, or leave it alone. And if it should be built, we can build it.