Capabilities / Software, Apps & AI
Software built by people who will explain it.
Scope. Build. Hand over.
Custom software, SaaS platforms, mobile apps, and AI. Built to be owned by you, documented well enough to be maintained by anyone, and scoped honestly enough that the number at the end matches the number at the start.
HAUS XXIV builds custom software, SaaS platforms, mobile and web apps, and custom AI. Every engagement starts with a paid discovery phase priced separately, producing a technical requirements document, an architecture diagram, and a phased cost range. Source code lives in the client's repository from the first commit.
Most custom software projects fail quietly.
Not in a dramatic way. The budget doubles, the timeline triples, and eighteen months later there is a system nobody fully understands, held together by one developer who is starting to look around. The documentation was never written. The scope was never honest. Every change request became a negotiation.
01 / WHAT WE BUILD
Four capabilities. One backbone.
Internal tools, client portals, workflow systems, and the integrations that stop your team from copying data between four platforms by hand. Real growth needs real infrastructure underneath it, and most companies hit a ceiling not because of demand but because their operations run on a spreadsheet somebody made in 2019.
WHAT SHIPS
- Technical architecture and data model documentation
- Custom application, front end and back end
- API design and third-party integrations
- Role-based access control and audit logging
- Automated test suite with documented coverage
- Deployment pipeline and environment documentation
Multi-tenant products built to be sold, not just used. Subscription billing, onboarding, admin tooling, and the unglamorous infrastructure that decides whether a product survives its first hundred paying customers.
WHAT SHIPS
- Multi-tenant architecture with data isolation
- Subscription billing and plan management
- User onboarding and account provisioning flows
- Admin and support tooling for your team
- Usage analytics and product instrumentation
- Security review and penetration test coordination
Native and cross-platform apps with product thinking from screen one. An app is not a website in a smaller frame. It lives in a pocket, gets opened in bad light with one thumb, and competes with every notification on the device.
WHAT SHIPS
- iOS and Android builds, native or cross-platform
- Full product design and interaction specification
- Offline behavior and state handling
- Push notification architecture
- App Store and Play Store submission and listing assets
- Release process documentation and crash reporting
Assistants, automation, and model integration built for a specific job with the guardrails written before the feature. We work with AI partners on the model layer and build the product layer ourselves, which means you get current capability without betting your business on a single vendor's roadmap.
WHAT SHIPS
- Use case assessment with an honest go or no-go recommendation
- Model selection and integration architecture
- Retrieval systems over your own documents and data
- Evaluation harness so quality is measured, not assumed
- Guardrails, human-in-the-loop checkpoints, and audit logging
- Cost modeling per user and per query before you commit
02 / NO AMBIGUITY
What actually lands in your hands.
Discovery
- Technical requirements document
- Data model and system architecture diagram
- Integration map for every external system
- Phased build plan with cost range per phase
- Risk register naming what could go wrong and what it costs
- Clickable prototype of the core workflow
Build
- Source code in a repository you own, from day one
- Automated test suite with coverage reporting
- API documentation generated from the code
- Staging environment open to you throughout
- Weekly written build note and a live demo every two weeks
Handover
- Deployment and infrastructure documentation
- Runbook for the failures that are actually likely
- Admin training, recorded
- Security review findings and remediation log
- Named support window with response times in writing
03 / HOW SOFTWARE GETS BUILT
Five phases. Discovery comes first, always.
We do not quote a build we have not scoped. Discovery is paid, separate, and yours to keep. If you take those documents to another firm, we will have still done our job.
01 / 05
01
Discovery
Two to four weeks, priced on its own. We map the workflows, the data, the integrations, and the edge cases that nobody mentions until month five. You end with a real technical spec and a phased cost range built on evidence instead of optimism.
Ends with: Requirements document, architecture diagram, phased estimate, and a clickable prototype.
02
Architect
Data model, system architecture, security model, and infrastructure decisions made deliberately and written down. This is the phase that determines whether year three is a pleasure or a rewrite.
Ends with: Approved architecture and a written technical decision record.
03
Build
Two-week cycles with a working demo at the end of each one. You see real software running, not a status percentage. Code lives in your repository from the first commit, so ownership is never a conversation we have to have later.
Ends with: Working software in staging, demoed every two weeks.
04
Harden
Automated tests, load testing, security review, and accessibility. We try to break it on purpose, including the failure modes that only appear under real concurrency. Nothing ships on the assumption that it probably holds.
Ends with: Test coverage report, load test results, security findings and fixes.
05
Launch and hand over
Deployment, documentation, and training built for the developer who joins your team next year and has never met us. Then a named support window with response times in the contract, not implied by goodwill.
Ends with: Production deployment, runbook, recorded training, and a written support agreement.
04 / WHY THIS HAUS
Three reasons, and the code behind them.
PRINCIPLE 12
AI is a tool. Not a shortcut.
Humans stay on the wheel.
We use AI to accelerate the people building your system, and we build AI features that keep a human in the loop where the decision carries weight. Every AI system we ship logs what it did so you can audit it. We don't replace evolving. We replace laziness.
PRINCIPLE 02
Educate. Don't dictate.
You will not be locked in.
Code lives in your repository from the first commit. Infrastructure runs in your accounts. Documentation is written for a developer who never met us. If you outgrow us or simply want to move on, you can, and nothing breaks on the way out.
PRINCIPLE 10
No ego. All output.
We will tell you not to build it.
A meaningful share of the software people ask us to build should not exist. Sometimes the answer is a configured off-the-shelf tool costing a fraction of a custom build. We say that out loud, early, even though it costs us the project. The work wins, or nobody does.
05 / THE STACK
- TypeScript
- React
- Next.js
- Node.js
- Python
- PostgreSQL
- React Native
- Swift
- Kotlin
- AWS
- Vercel
- Supabase
- Stripe
- Docker
- GitHub Actions
- Playwright
We choose boring, proven technology on purpose. Your system has to be maintainable by developers we have never met, five years from now, without a specialist who only exists at this haus. Novelty in a stack is a cost you pay every year.
How we approach custom AI06 / STRAIGHT ANSWERS
Software questions, answered plainly.
Discovery runs low five figures depending on complexity, and it is priced and contracted separately. Build cost comes out of discovery as a phased range rather than a single number, because a single number before scoping is a guess dressed as a commitment. Most first phases we deliver land in the mid five to low six figure range.
Because the alternative is a free estimate built on assumptions, which is how software projects double. Discovery produces a document you own and can take anywhere, including to another firm. If you do that, we still did the work honestly. Free estimates are not free. You pay for them later, with interest.
You do, from the first commit. Your repository, your infrastructure accounts, your name on the licenses. There is no scenario where leaving us means losing access to your own system. Agencies that host your code on their accounts are holding a leash and calling it a service.
We build the product layer and work with AI partners on the model layer. That is an honest description of the arrangement. What we will not do is tell you a language model is the right answer when a database query and a cron job would solve it for a hundredth of the cost. We start every AI conversation with whether you need one.
A named support window with response times written into the contract, not implied. Beyond that, a monthly retainer if you want us maintaining and extending it, or a clean handover to your team if you do not. Both are real options and we will not make the second one difficult.
Got a system your team is working around?
Tell us what breaks and where the manual work is. We will tell you honestly whether it needs a build or a fix.