Software for the operations
off-the-shelf platforms can't run.
Internal tools, customer-facing apps, and integrations between systems that don't talk. Designed, built, hosted, maintained — end to end.
Three shapes of software we build.
Internal operations tools
Quoting tools, inventory dashboards, order workflows, custom reporting — the apps your team runs the business with.
Customer-facing applications
Portals, configurators, marketplaces, booking systems — software your customers touch that has to feel like the brand.
Integration layers
When two systems don't talk, someone fills the gap with manual work. We build the layer so the data moves itself.
The whole lifecycle. One accountable partner.
Discovery and architecture
Map the actual problem before any code. Understand the operation, the constraints, the integration points — then build.
Web application development
TypeScript, Astro, Node, Postgres — the stack chosen for the problem. Built for reliability and long-term evolution.
Database design and management
Schema, migrations, backups, performance. The data layer treated as critical infrastructure.
Auth, billing, integrations
User authentication, subscription billing, integrations with the systems you already run. Wired in once, maintained from there.
Hosting and uptime
Production hosting, monitoring, alerts, security updates. The system runs — observed and maintained, without you watching.
Owned and maintained
Software isn't shipped and forgotten. Bug fixes, security patches, feature evolution as the operation grows.
The system runs. You go run the business.
- You stop bending off-the-shelf platforms to do what they weren't built for.
- You stop worrying about whether the system is patched, monitored, and backed up.
- You stop chasing developers when something needs to change.
- You stop owning the operational risk of software you don't control.
Software rarely lives alone.
Internal tools usually need a public face — that's Websites. Customer-facing apps usually need workflows around them — that's Automation. Same operating model across all three.
Common questions about the Software pillar.
- When does it make sense to build custom vs. use off-the-shelf?
- Off-the-shelf wins when the problem is generic. Custom wins when the operation has a specific shape that off-the-shelf forces you to compromise on, or when stitching multiple platforms costs more than building one well-fit system. We'll tell you which on the introduction.
- What stack do you build on?
- TypeScript end-to-end by default. Astro for content surfaces, Node or Bun on the server, Postgres for data, Vercel for deployment. The stack matches the problem.
- What does ongoing ownership look like in practice?
- The software runs on infrastructure we own and operate, maintained by the engineers who built it. Bug fixes, security patches, integrations, feature evolution — part of the engagement. Closer to outsourced engineering than a one-time build.
- How is software priced?
- Fixed-fee bundled by phase, not by hour. Pricing is scoped per engagement on the introduction.
- Do you also handle hosting and ongoing maintenance?
- Yes. Hosting, monitoring, security updates, feature evolution — part of the engagement. We don't build software and walk away.
Tell us about your business.
We respond within one business day with next steps or a introduction invite.