Six ways to work with us
Every engagement ends with software you own and can read. The differences are in scope, pace and how long we stay. Automation has its own page.
Web product development
Customer portals, dashboards, internal tools and the APIs behind them. We build in Next.js with a Kotlin or Node backend and PostgreSQL, deploy to EU infrastructure and leave you with a repository your next developer can pick up.
What you get
- Discovery and a written scope before any code
- Working software every two weeks on a staging address
- Tests, CI and a documented deployment
- Login, roles and multi-language from the start
Stack
Example: Wohnster, a landlord and tenant platform, currently in development.
Mobile apps
iOS and Android apps that share the backend, the login and the data model with your web product. One release process, one team, and no second truth about your data.
What you get
- One codebase for iOS and Android where that fits, native where it does not
- App Store and Play Store setup and releases
- Push notifications, offline state and sign-in reused from the web
- The same API as the web product, documented
Stack
[TODO: confirm the mobile stack SteinByte wants to commit to]
MVP builds
A first version with real users in weeks: the smallest product that answers your open question, on a foundation you keep instead of throw away. Fixed scope, fixed price, a date.
What you get
- A one-week scoping workshop with a written plan
- The product live on your domain, with login and analytics
- A feedback round after the first users
- A clear list of what was left out, and why
Stack
Typical length: [TODO: weeks]. Typical budget: [TODO: range].
Product partnership
We stay after launch. A fixed monthly capacity for features, maintenance, dependency upgrades, monitoring and the questions that only come up in production. You plan the roadmap, we keep the product healthy.
What you get
- A monthly plan agreed with you, shipped in two-week cycles
- Monitoring, backups and security updates handled
- A named contact who knows the codebase
- Quarterly review of costs, risks and the roadmap
Stack
A monthly retainer sized by capacity, cancellable with [TODO: notice period]. Starting at [TODO: price] per month.
Compliance-aware delivery
GDPR, data residency and audit trails are designed in from the first sprint rather than bolted on before an audit: EU hosting, role-based access with Keycloak, documented data flows, deletion that actually deletes.
What you get
- A data map: what is stored, where, for how long, who can see it
- Access control and audit logging built into the product
- Infrastructure in the EU with a documented processor list
- Input for your records of processing and privacy policy
Stack
We are engineers, not lawyers: we build what your data protection officer specifies and document it so they can check it.
AI-augmented delivery
This is how we work, not a product we sell. AI tools draft code, write tests and review changes alongside us, so a small team ships at the pace of a larger one. Every change is still read, understood and signed off by a person before it reaches you.
What you get
- Faster first versions and faster fixes
- More tests than a team this size would usually write
- Documentation that exists because it is cheap to keep current
- Your code and data never used to train anything
Stack
What it does not change: a person is responsible for every line we deliver; code review, CI and staging stay mandatory; architecture and security decisions are made by us, not generated.
Not sure which one fits?
Describe what you are building and we tell you which engagement we would propose, and what it would roughly take.