We do not list twenty things we could theoretically take on. Custom software development, the parts of it we are actually good at: the application at a desk and the app in people’s hands, the marketplace, the CRM and the client portal built around one company’s process, the tests that catch a bad release, and the pipeline that ships it. Building since 2014. If your project is none of these, we will say so plainly rather than learn on your budget.
Web applications and platforms — the kind with accounts, roles, data and money moving through them. Also the marketing site in front, when it has to load fast and convert.
Custom CRM for businesses whose pipeline, pricing or approvals no longer fit a boxed product. Your stages, your rules, your history imported, and no per-seat fee for the people who only need one screen.
iOS and Android, native or cross-platform depending on what the product actually needs. From a first release that proves the idea to a product in both stores.
A portal where your customers see their own orders, documents and balance, and can do one thing about it themselves. Reads from the systems you already run rather than keeping a second copy.
Two-sided platforms where buyers and sellers transact: escrow between them, commission taken automatically, disputes with deadlines and an outcome, and payouts that survive failing.
End-to-end tests for the product you already run, on the web and on mobile. A suite in your repository, wired into your pipeline, green on every push.
Automated builds and deployments for a product that already exists, with monitoring, backups you have seen restored, and an optional arrangement for keeping it all alive.
Repository, accounts and infrastructure are yours from day one. Leaving us should cost you nothing but a handover call.
A range, what it rests on, and what would move it. A single exact figure before the work starts is a marketing number.
Including out of hiring us, when an existing product would serve you better. It costs us a project and saves you a year.
Most of our work sits under NDA, so instead of a client list we write up the kinds of products we build and what is genuinely hard inside them — with prices and a demo you can open. See the case studies.
What tends to come up before a project starts — budgets, timelines, and what to decide first.
Everyone agrees on starting small and nobody agrees on how small. The rule that has worked for us: one journey, all the way through, including its bad days.
Nobody has the budget to cover every screen, and covering every screen would not help anyway. A short, opinionated method for choosing the first fifteen journeys.
One codebase or two is the first real decision in a mobile project and the one most often made for the wrong reasons. Four questions that settle it.