Mr Mubin
Chief Executive Officer
Client relationships and the commercial shape of every engagement.
Ahmedabad, India — serving four markets
Software for the problems that don’t fit a template.
We build custom platforms, ERP systems, mobile apps and cloud infrastructure for businesses whose process is the reason off-the-shelf software keeps failing them. Twelve services, six industries, one team that writes down what it finds.
- Paid discovery you keep, whatever you decide next
- Source in your repository from the first commit
- No lock-in, one month’s notice, both ways
- 4
- countries served across India, the US, the UK and Australia
- 12
- services across build, run and grow
- 6
- industries with domain models we have already built
- 161
- screens in design on SPARRAPS, our current product
What we do
Twelve services across build, run and grow
Grouped by what they are for, because a flat list of twelve makes it impossible to tell which one you actually need.
- BuildCustom Software DevelopmentCustom platforms, marketplaces and SaaS. We write the parts that are specific to your business and buy the parts that aren’t.Read more
- BuildWeb Application DevelopmentDashboards, portals and internal tools that hold up under real data volumes — not a prototype that falls over at ten thousand rows.Read more
- BuildMobile App DevelopmentReact Native when one codebase is genuinely enough. Native when it isn’t — and we will tell you which before you commit a budget.Read more
- RunERP SolutionsImplementation, plus the custom modules the implementation always turns out to need in month four.Read more
- RunCloud & DevOpsDeploys that are boring on purpose. Infrastructure as code, real environments, and a bill you can read line by line.Read more
- GrowUI/UX DesignProduct design and design systems. Usually the first thing that turns out to be wrong, and the cheapest thing to fix.Read more
How we work
Discovery first. Then slices, never layers.
Six steps, and the first one is a conversation that sometimes ends with us telling you we are not the right people.
- Discovery is paid, written down, and yours to take anywhere
- Each slice is deployed and usable, not a horizontal layer
- Handover ends when your team can deploy, roll back and restore unaided
First conversation
Thirty to sixty minutes, no charge and no deck. You describe the problem, we ask the questions that usually reveal whether it is the problem. If we are not the right people for it we say so on that call, and we usually say who is.
Discovery — paid, two to three weeks
We sit with the people who do the work, not only with the people who commissioned it. The output is a written model of your domain, a build order and a real number. All three are yours to keep, and to take elsewhere, whether or not you continue with us.
Shape
Screens and data model worked out together, because one always breaks the other. Design system first, screens second. This is where scope gets cut deliberately rather than discovered as a schedule problem later.
Build in slices
Each slice is a working, deployed, usable piece of the system rather than a horizontal layer of it. Two-week cadence, demoed against real data. If the budget stops, you stop with something that runs.
Harden
Load testing at realistic volumes, an access-control review, and the failure paths — what the system does when the payment gateway is down, not only when it is up. Monitoring and alerts wired before launch rather than after the first incident.
Handover
Documentation, a recorded walkthrough, and your team performing a deploy, a rollback and a restore themselves while we watch. If they can do all three unaided, the handover is complete.
Industries
Six sectors whose exceptions we already know
Every industry has rules nobody wrote down. These are the ones where we have already found them, and can tell you what usually breaks.
- ManufacturingProduction planning, job-work tracking and quality records for plants where the real process never matched the ERP’s idea of it.What breaks here
- Retail & E-commerceCatalogue, pricing and inventory across storefront, marketplace and shop floor, reconciled to one number rather than four.What breaks here
- Logistics & Supply ChainDispatch, fleet and proof-of-delivery systems built for drivers on bad connections, not for the demo on office wifi.What breaks here
- HealthcareClinic, diagnostic and patient-record systems where the audit trail and the consent model are part of the architecture.What breaks here
- Education & EdTechAdmissions, learning delivery and assessment platforms that survive an intake week without falling over.What breaks here
- Real Estate & ConstructionInventory, booking and site-progress systems for developers running several projects and several sales channels at once.What breaks here
Technologies
Boring on purpose
We choose the option with the largest hiring pool and the longest support window — so you can hire someone to maintain this without us.
Frontend
Backend
Mobile
Data
Cloud
Why us
Six positions we will not trade away
Every one of these costs us work occasionally. That is roughly the point — they are the things you can hold us to.
Discovery is paid, and portable
A free "discovery" that produces a proposal is a sales meeting. A paid one produces a specification you own and can take to any other firm. We think that is the honest version, and it is why we charge for it.
Slices, not layers
Building the database, then the API, then the interface means nothing works until everything works. Building one narrow path all the way through means you can use it in week three and correct us in week four.
Your repository, from commit one
Code lives in your organisation account, not ours. There is no escrow, no licence-back and no per-seat fee on something you paid to have built. Leaving is a normal ending, not a penalty.
Written by default
Decisions get recorded, not just discussed. Across four time zones a written decision record is worth more than any number of calls, and it is what makes a handover possible at all.
Boring technology
We choose the option with the largest hiring pool and the longest support window, not the one that is interesting this quarter. You should be able to hire someone who can maintain this without us.
We say no
To work we would do badly, to a language model where a rule belongs, and to a timeline that can only be met by shipping something we would not run ourselves. Turning down work is the cheapest form of quality control.
The team
Four people, and you will meet all of them
No account manager between you and the person writing the code. The CTO reviews every change, including ours.
Mujib
Managing Director
Delivery oversight, resourcing and the schedule you are actually held to.
Afroze Saiyed
Chief Financial Officer
Contracts, invoicing and the cost model behind every estimate we send.
Vasim Shaikh
Chief Technology Officer
Architecture, code review and the technical decisions that are hard to reverse.
Before you call
The questions everybody has
Cost, ownership, what we need from you, and what happens if it goes wrong.
Why won’t you quote from our requirements document?
Because a number quoted against a requirements document written before anyone has examined the domain is a guess with a decimal point on it. Both sides discover that around month four, when the number stops being true and the relationship becomes a negotiation. We would rather charge a modest fixed fee for two to three weeks of discovery, produce a specification grounded in how your business actually works, and quote against that. If our number is then wrong for you, you still own the specification and can take it anywhere.
What does discovery cost, and what do we get?
A fixed fee agreed before it starts, scaled to the size of the domain — for most engagements it is a low five-figure sum in rupees and takes two to three weeks. You get a written model of your domain: the entities, the states they move between, the rules that govern the transitions, and the exceptions we found that nobody had written down. Plus a build order and a real estimate. All of it is yours, in writing, whether or not you continue with us.
Who owns the code and the intellectual property?
You do, from the first commit. Work happens in your repository under your organisation account, not in ours. There is no escrow arrangement, no licence-back clause and no per-seat fee on something you paid to have built. If you stop working with us tomorrow, everything keeps running and any competent team can pick it up. We think a firm that needs to hold your code to keep you has already told you something about the work.
What do you need from us?
One person with the authority to make decisions, available for roughly two hours a week. That is genuinely the most important input, and projects stall on its absence more often than on anything technical. We also need access to the people who do the work — not only the people commissioning the software — because the exceptions that decide the architecture live with them.
What technologies do you work with?
TypeScript, React and Next.js on the front end; Node.js on the back end; PostgreSQL as the default database; React Native for mobile; AWS for infrastructure. We also work in .NET, Laravel and Flutter, mostly where an existing estate or team makes that the right answer. The selection principle is deliberately dull: the largest hiring pool and the longest support window, so you can hire someone to maintain this without us.
What happens if we want to leave mid-project?
You leave. One month’s notice, we finish or cleanly stop the current slice, and we spend the remaining time on handover rather than on new work. Because each slice is a working piece of the system, you stop with something that runs rather than with a half-built layer. We would rather end an engagement well and be recommended than hold on to one that is not working.
Tell us what keeps not working.
One call, no deck, no obligation. We will tell you whether this is a software problem, and whether we are the right people for it.