Founder note
Chaudhry Shafan Arshad
That turns out to be most of what a service business does every day, and almost none of it is written down anywhere you could check.
The route in
My training is actuarial. The job is to take a domain governed by hard rules and uncertain outcomes, quantify it honestly, and produce a number you can defend to someone who wants it to be a different number.
Two habits come out of that and they have shaped everything since. Assumptions get sourced, not inherited. And the working is shown, because a number nobody can audit is an opinion wearing a decimal point.
Building software was not a change of subject. A quoting engine is an actuarial problem with a user interface. So is an inspection schedule, a stock reorder point, and a formulation that has to survive a warehouse in July.
What it looks like
The two builds on this site have nothing in common on the surface. One runs a licensed electrical contractor. The other is a cluster of nine agents designing a supplement.
Underneath, they are the same exercise: rules that constrain a correct answer, encoded so a machine can compute it and a person can check it.
On the contracting build, rebuilding the pricing basis from the code itself turned up a permit fee being charged to customers that did not legally exist. Nobody had been careless. It was simply that nothing had ever read the rules end to end against what the pricing engine actually did. That is what sourcing assumptions is for, and it is worth more than any feature I have ever shipped.
How I work
Regulatory rules get verified against the regulator, with the date the rule takes effect recorded. On one build, two editions of the electrical code were valid at the same time during a transition, and the pricing had to know which was which.
When automation is the wrong tool, when the fix is a process change rather than software, and when a job is too small to be worth paying me for. A consultant who never talks you out of anything is selling, not advising.
Pricing rules live in one place you can read and change. Failures announce themselves rather than passing silently. If a decision matters, you can trace how it was reached.
If I have not measured it, I will say so rather than estimate it into a slide. It costs a little persuasion and it is the whole basis of being useful to you afterwards.
Practicalities
I am based in Sialkot, Pakistan, and I work Toronto hours, so I am online through your working day rather than replying to it the next morning.
The system described on this site has run a Canadian contractor's operation for a year and I have never been in the building. Field service is unusually well suited to this, because the work already happens through phones, forms and software rather than across a desk.
Everything runs in your accounts, on your payment methods, in your name. Hosting, telephony, model providers, accounting seats. You see every running cost directly, and you can revoke my access in an afternoon without asking me. That is deliberate, and it is the arrangement I would want if I were you.
Straight answer
One deep client, not a client list.
I am not going to describe a roster I do not have. One contractor, in depth, over a year, and a multi-agent formulation system for a sports nutrition company. That is the honest inventory.
What I can do instead of references is show you a real system running, and start with a week of work priced so that finding out what I am like to work with costs you very little. If it turns out there is nothing here worth building, that is a useful answer too and you will get it from me directly.
Contact
Tell me how a job travels through your business today. A whiteboard is a perfectly valid answer.