What we build. What's in, what's out, and what you're left holding.
All four come with the same terms: the scope is closed before any code is written, the code is yours and the infrastructure is in your name. What changes is what gets built.
Custom software
A system built around how your company works today. Not someone else's product configured until it roughly resembles what you do: the screens are the steps your team already takes, with the names it already uses.
Who it's for
For anyone running the operation across spreadsheets, a notebook and three separate group chats, who has already lost money because something was sitting in one of the three and nobody looked at it in time.
What's included
- A walkthrough of how the operation runs and a defined scope, both closed before any code is written
- Screen design and data model, approved by you
- Development, with something you can click on every week
- Roles and permissions: who sees what and who can approve what
- Your real data loaded in for testing
- Launch on infrastructure in your name
What isn't
- Migrating data that isn't in a file yet: if it lives in someone's head, it has to be written down first
- Integrations with systems that have no API and no export, where the only way through is copying by hand
- Loading historical data, quoted separately because it depends on what shape it's in
- Hardware support: scanners, scales, receipt printers
What you're left holding
- The system running, with your data in it
- The code, all of it, in a repository you own
- The infrastructure in your name, with the keys
- Documentation of how it's put together and how it deploys
- A training session with the team that's going to use it
Mobile apps
An app on the phone of whoever works away from a desk: the driver on a route, the rep visiting clients, the foreman filing a report on site. Native or cross-platform depending on who it has to reach and what parts of the phone it has to talk to.
Who it's for
For the operation that already happens out in the field and gets written down at night, from memory, into a spreadsheet. What you gain isn't convenience: it's the data going in at the time and place where it's still true.
What's included
- One app for iOS and Android, from a single codebase unless there's a reason to split them
- Works with no signal, syncs when it comes back
- Camera, location and notifications where the flow needs them
- The web dashboard where you see what the apps send in
- Publishing to the App Store and Google Play
What isn't
- The Apple and Google developer accounts, which go in your name and have their own annual cost
- Whatever the stores decide in review: we prepare it to pass, we don't guarantee how long they take
- Builds for operating system versions the manufacturer no longer updates
- Keeping the app published forever: the stores ask for periodic updates, and that's maintenance
What you're left holding
- The app published in both stores, under your accounts
- The code for the app and for the dashboard
- The store listings: copy, screenshots and icons
- The release process documented, so the next version doesn't depend on us
Working examples
SaaS development
A product you sell to many customers, not a system for your own company. Everything underneath changes: each customer has to see only their own data, someone has to be able to sign up without you stepping in, and the charge has to go through every month without anyone pushing it.
Who it's for
For anyone who already solved one specific problem for their industry —sometimes inside their own company— and wants to sell it. And for anyone who wants to stop charging by the hour and start charging by the month.
What's included
- Multi-tenant: every customer's data isolated from everyone else's
- Sign-up, free trial and plans, with no input from you
- Subscription billing wired in, with invoicing and retries
- An admin panel to see accounts, usage and payments
- The numbers that run the business: sign-ups, cancellations and which plan people move to
What isn't
- The payment gateway account and its fees, which go in your name
- Pricing strategy: the system supports the plans you define, it doesn't define them
- Marketing, acquisition and selling the product
- Compliance certifications like SOC 2 or HIPAA, which are a project of their own
What you're left holding
- The product in production, with the first plan actually charging
- The code and the infrastructure in your name
- The admin panel and the business dashboards
- Documentation of the data model and of how a new plan gets added
AI features
A model dropped into a step a person does by hand today: reading a packing slip and keying it in, answering the same question for the tenth time, going through a hundred photos to find two. The hard part isn't the model: it's getting the result into the system you already use, and making it visible when the model isn't sure.
Who it's for
For anyone with a repetitive task, at volume, with a result you can check. If you can't check it, it isn't a good first AI project: it's a source of errors nobody is going to catch.
What's included
- The use case picked with you, starting with the highest volume and the lowest risk
- The feature running inside your system, not in a separate tool
- Human review where it's needed: the model proposes and a person confirms
- It shows when the model isn't sure, instead of making something up with the same straight face
- Control over what each query costs, with caps
What isn't
- Training a model of your own from scratch: we use the ones that already exist, which is what makes sense for almost every case
- Guaranteeing zero errors. A model gets things wrong; what gets designed is what happens when it does
- Model usage, which is paid per use and goes on your account
- Cases where a simple rule is enough: there AI costs more and is harder to audit
What you're left holding
- The feature in production, integrated into the system
- The code and the prompts, versioned as code
- The provider accounts in your name
- A measurement of how often it gets it right, run on your own cases
Working examples
Does any of these look like what you need?
Half an hour, free, to understand what you need. If we can build it, you leave the call with the scope, the timeline and the price; if we can't, we tell you right there.