Software for the operations
off-the-shelf platforms can't run.
Internal tools, customer-facing apps, and integrations between systems that don't talk to each other. Designed, built, hosted, and maintained — by one accountable partner, end to end.
Three shapes of software we build.
Internal operations tools
Quoting tools, inventory dashboards, order workflows, custom reporting — the apps your team uses every day to run the business.
Customer-facing applications
Portals, configurators, marketplaces, booking systems — the software your customers interact with that should feel like an extension of the brand.
Integration layers
When two systems don't talk, the gap is usually filled with manual work. We build the layer between them so the data moves on its own.
The whole lifecycle. One accountable partner.
Discovery and architecture
Map the actual problem before any line of code. Understand the operation, the constraints, and the integration points so the build solves the real problem.
Web application development
TypeScript, Astro, Node, Postgres — the stack chosen for the problem, not for fashion. Built for reliability and long-term evolution as the business changes.
Database design and management
Schema, migrations, backups, performance. The data layer treated as infrastructure, not as an afterthought.
Auth, billing, integrations
User authentication, subscription billing, and integrations with the systems you already run. Wired in once, maintained going forward.
Hosting and uptime
Production hosting, monitoring, alerts, security updates. The system runs, observed and maintained — without you needing to think about it.
Tended after launch
Software isn't shipped and forgotten. Bug fixes, security patches, feature evolution as the operation grows. One accountable partner for the whole lifecycle.
The system runs. You go run the business.
- You stop trying to bend off-the-shelf platforms to do something 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 where Websites comes in. Customer-facing apps usually need workflows around them — that's where Automation comes in. Same accountable partner 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 and the platform is good enough. Custom wins when the operation has a specific shape that off-the-shelf forces you to compromise on, or when integration costs of stitching multiple platforms exceed the cost of building one well-fit system. We'll tell you honestly which side you're on, on the discovery call.
- 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 or your hosting choice for deployment. The stack matches the problem; we don't pick stacks for novelty.
- 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, integration changes, and feature evolution are part of the engagement — not extras. The model is closer to outsourced engineering than a one-time custom build.
- How is software priced?
- Fixed-fee bundled by phase, not by hour. Software pricing is scoped per engagement; we anchor it on the discovery call before any contract.
- Do you also handle hosting and ongoing maintenance?
- Yes. Hosting, monitoring, security updates, and feature evolution are part of the tending. We don't build software and walk away.
Tell us about your business.
We respond within one business day with next steps or a discovery-call invite.