We build your software.
You own it.
There's a process in your business that only works because someone remembers to do it. I build the software it should have been, on your real data, then stay on as your technical partner.
- SKU-1042Forecast up 18%, open PO shortShort
- SKU-0877Supplier hasn't confirmed ship dateChase
- SKU-2210Committed twice across two plansReview
The process runs on one person's Thursday.
Every week someone exports a report, pastes it into a sheet, checks three inboxes and posts a summary in Slack. It works, as long as they're in. When they're off, it quietly stops, and you find out a week later.
Export the forecast from the ERP into the planning sheet
Monday · CopyingCross-check open POs by hand, one supplier at a time
Tuesday · CheckingEmail suppliers who haven't confirmed, then wait
Wednesday · ChasingThe buy deadline passes with a shortfall nobody saw
Friday · Too late
Buy a tool, build it in-house, or build it with me.
| Buy another tool | Build it in-house | Modh | |
|---|---|---|---|
| Who designs it | The vendor's template | Your engineers, when the roadmap allows | The people who do the work, with me |
| Where it runs | Their cloud, one more login | Your stack | Your stack and your cloud accounts |
| Who owns the code | The vendor | You | You, from the first commit |
| Who keeps it working | The vendor, on their roadmap | Whoever built it, until they move on | Me, as your ongoing partner, or your team after handover |
| When it's live | A quarter of rollout | Days to a demo, months to trust it | Working on your data within a couple of weeks, then shipped in slices |
| If you stop paying | It's gone | Not applicable | You keep everything |
Start small. Stay as long as it's useful.
How we work →Walk-through
30 minutes, freeShow me the workflow that hurts most. You get a one-page scope in two working days, or an honest no.
First workflow
Fixed feeWorking on your data within two weeks. If it isn't earning its keep by then, we stop and you don't pay the rest.
Partnership
MonthlyI stay on and build what's next, on a roadmap we review every month. A month's notice to stop.
Handover
Any timeYour team takes the repo, the runbook and the recordings. No exit fee.
Workflows that should have been software years ago.
Supplier commitments
Nets the forecast against open POs and flags what's short before the buy deadline.
Built for an industrial operations company
Lead routing and call prep
Books each lead with the right rep and writes the brief from CRM history before the call.
Built for an AI sales platform
Month-end books
Pulls bank transactions, matches receipts, and hands your accountant a ledger they can file from.
Built for Modh's own books
Weekly operating digest
Reads tickets, pull requests and Slack, then writes the Monday update leadership actually reads.
Built for an engineering team
Customer request triage
Reads the request, pulls the account history, and routes it to the person who can fix it.
Not built yet. Ready to scope.
Client onboarding
Turns a signed deal into the kickoff doc, the tickets and the shared channel, without anyone retyping it.
Not built yet. Ready to scope.
Nothing leaves your accounts that you didn't approve.
- It runs in your accounts. Hosting and AI usage bill to you directly.
- SSO, roles and an audit log by default. Including every action an AI model suggested.
- Models can be swapped as better ones ship. No rebuild needed.
You work with me, start to finish.
I'm Imran Gardezi. I've spent more than fifteen years building production software, including at Shopify and Brex. There's no sales team and no handoff to juniors. The person who maps your workflow is the person who writes the code and answers the phone when it breaks, which is why I only work with a few teams at a time.
Based in Vancouver with roots in Ireland.
More about me →
Which workflow would you hand off first?
Walk me through it in thirty minutes. If it's a fit, you'll have a one-page scope in two working days. If it isn't, I'll tell you what I'd do instead.
Form not loading? Open the booking page