AI Product Consulting · Islamabad → Worldwide
I cannot writeproduction code.I have shipped six products.
Not a paradox. Building software became a specification problem, and specification is an operator skill.
Or get the weekly newsletter
[PLACEHOLDER: real subscriber count] operators and founders already subscribed
Weekly. One click to unsubscribe.
- NIC Islamabad · Cohort 12
- Co-founder & CEO, Triisum
- 6 products shipped
- $1M seed raise run
Watch first
The twelve-minute version of this page.
Everything on this page, explained out loud, with the screen share. · 12:04
No pitch on the first call. If I am not the right fit I will say so in the first ten minutes.
Nothing loads from YouTube until you press play. No cookies are set before that.
Who this is for
Three people get disproportionate value from this. You are probably one of them.
If you are not on this list, the newsletter is free and there is no reason to book a call.
01
The solo founder who is the bottleneck
You can see the whole product in your head. You cannot build it fast enough to find out if you are right. Every week you spend building is a week you are not learning. You do not need a co-founder yet; you need leverage.
Indie · bootstrapped · pre-seed
02
The product team stuck in the pilot phase
Someone bought the licences. A few engineers use it for boilerplate. Nothing about how you ship has actually changed, and leadership is starting to ask what the spend bought. The problem is not adoption. It is that nobody rebuilt the workflow around it.
Seed → Series B · 5–50 people
03
The operator who will never learn to code
You run marketing, or ops, or the whole business, and you have made peace with not being technical. You keep hearing AI should be doing half your job and cannot work out which half. You do not want to become a programmer. You want to stop paying three weeks for something that should take an afternoon, and this is the group I came from, so it is the one I can be most useful to.
Marketers · founders · business owners
How I found this
For four years I was the guy who could not build his own product.
I co-founded Triisum in 2021 and ran it as CEO. I did the parts an operator does: 50+ customer interviews, the white-label partnerships, the OTA integrations, the NIC Islamabad cohort, an eight-person team across engineering, QA and ops. What I could not do was build any of it. Every idea I had went into a queue, and the queue was other people, and the queue was always full.
You learn a specific kind of patience running a company you cannot personally build. You get very good at writing specs, because the spec is the only lever you have. You also get very good at watching a two-week estimate become six, because the thing in your head and the thing in the engineer's head were never the same thing and neither of you found out until the demo.
So when the AI coding tools arrived I did what every non-technical founder does. I typed what I wanted in a sentence, the way you would ask a person. And I got back what everyone gets back: something that runs, looks roughly right, and is wrong in a way that takes longer to unpick than to rewrite. I concluded the tools were for engineers and went back to the queue.
What changed was realising I had been treating it like a search engine (short question, magic answer) when it is closer to an extremely fast, completely literal contractor with no memory of yesterday and no ability to ask you a clarifying question. So I stopped writing prompts and started writing **the brief I had already spent four years learning to write for humans.** Constraints. Edge cases. The file it goes in. What "done" means. What it must not touch.
The output stopped being wrong. Same model that afternoon as that morning: the difference was that for the first time the specification was actually complete, and I only knew that because something had executed it literally enough to expose every gap. Since then I have shipped LittleOS, Liquid Finance, Safar, ThumbSnap AI, an autonomous publishing pipeline, and the Eco-Ambassadors app. I still cannot write production code.
That is the whole argument. The four years of operator work were not the obstacle to building; they were the qualification for it, and I had it backwards the entire time. It took me months of doing this badly to see that. It takes my clients about three weeks, because they get to skip the months.
The thing I thought disqualified me was the thing that qualified me.
The one thing
If building software is now a specification problem rather than an engineering one, and if specification is a skill you already built by running a business, then being non-technical stopped being the reason you cannot ship, and quietly became the reason you can.
That is the only claim I am making and the only one that has to be true. If you believe it, the question stops being whether to build this capability and becomes how quickly you can install it. If you do not believe it, no offer, bonus or guarantee below is going to change your mind, and the honest recommendation is to read the newsletter for a few months and decide for yourself. The six products in the work section are the whole of my evidence. Go and look at them before you decide.
Consulting
Three ways to install this. They are the same system at three depths.
Every engagement starts with the same free call, and I will tell you on that call which of these you actually need, including when the answer is none of them.
The Strategy Call
Free
30 minutes
You describe what you are trying to ship and where it is stuck. I tell you what I would do. That is the whole call.
- A direct read on whether your bottleneck is spec, scope, or genuinely engineering capacity
- The specific first workflow I would change this week
- An honest answer on whether you need me at all
- Recording and written summary afterwards
The Build Sprint
Most picked[PLACEHOLDER: Build Sprint price]
2 weeks
We do not talk about the system. We use it, on your real codebase, to ship one thing you have been stuck on, and you keep the method afterwards.
- Two weeks working directly on your product, not a sandbox
- One real feature or MVP shipped to production
- Your specification templates, written against your actual stack
- Claude Code configured for your repo: CLAUDE.md, skills, hooks, permissions
- Recorded working sessions you can hand to a new hire
- Four weeks of async follow-up after we finish
Team AI Adoption
[PLACEHOLDER: Team engagement price]
90 days
For teams where the licences got bought and nothing changed. We rebuild the workflow around the tool instead of bolting the tool onto the workflow.
- Audit of how your team actually ships today, not how the process doc says they do
- Live training for product and engineering, run separately: they have different problems
- A shared spec standard the whole team writes against
- Repo-level configuration and review conventions
- Adoption metrics so leadership can see what the spend bought
- Monthly working session for the full 90 days
The risk is mine, not yours
If you finish the first week of a Build Sprint and do not believe it will pay for itself, tell me and I refund it in full. I have never had to, but the offer is real and it is in the contract: I would rather lose a fee than have someone tell five people it was not worth it.
Courses
Or learn it yourself, at a tenth of the price and four times the pace.
Consulting does not scale and most people do not need it. The courses are the same system, self-serve. Start with the free one: if it does not change how you work in the first hour, do not buy the others.
Course titles below are proposals. Rename anything.
- Start hereFree
Claude Code for Founders
The specification system, end to end, on a real project. The one I would send someone who has ten minutes and is sceptical.
- Write a brief an agent can execute without you babysitting it
- Set up CLAUDE.md so context survives between sessions
- Recognise the four failure modes before they cost you an afternoon
- Platform
- Free · by email
- Price
- Free
- Intermediate
AI Product Management
For PMs and founders who own the what and the why. Specs, scoping, and running a roadmap when implementation stops being the constraint.
- Rewrite your PRD format for a world where execution is cheap
- Scope work in agent-sized units instead of sprint-sized ones
- Run discovery when you can prototype the answer in an afternoon
- Platform
- [PLACEHOLDER: platform: self-hosted, Udemy, or Coursera]
- Price
- [PLACEHOLDER: course price]
- No code required
Claude for Marketers & Business Owners
Zero programming. For the operator who wants the three-week jobs to become afternoon jobs, and does not care how it works underneath.
- Build repeatable workflows for content, research and reporting
- Automate the recurring work without hiring or learning to code
- Know precisely where AI output still needs a human before it ships
- Platform
- [PLACEHOLDER: platform: self-hosted, Udemy, or Coursera]
- Price
- [PLACEHOLDER: course price]
Proof
Five clients. Here is what they say.
These slots are empty on purpose. Real quotes, with permission, or nothing (see CONTENT.md).
- Products shipped
- 6
- Clients advised
- 5
- People trained on AI tools
- 15+
- Following on LinkedIn
- 9K+
[PLACEHOLDER: Testimonial 1: the exact words, with permission to publish]
[PLACEHOLDER: Testimonial 2: the exact words, with permission to publish]
[PLACEHOLDER: Testimonial 3: the exact words, with permission to publish]
[PLACEHOLDER: Testimonial 4: the exact words, with permission to publish]
[PLACEHOLDER: Testimonial 5: the exact words, with permission to publish]
Work
Six products. None of them written by me.
This is the section that has to carry the whole argument, so it is the one with the least spin in it. Every project below is real, most are public, and the stacks are listed because a sceptical engineer reading this page will want to check.
- Open sourceIn development
LittleOS
A zero-cost AI operating system: multi-tenant, 50+ agents, voice control, installable as a PWA. The most ambitious thing on this list and the place I try ideas too unproven to run on a client engagement.
- Next.js 15
- TypeScript
- Supabase
- Cloudflare
- tRPC
- n8n
- PrivateLive · since 2021
Triisum
Travel eco-marketplace connecting tourists with agents, hotels and tour operators. Co-founder and CEO: 50+ customer interviews, 10+ white-label partnerships, 2 OTA integrations, NIC Islamabad Cohort 12 from 1,110 applicants.
- Marketplace
- Co-founder & CEO
- 8+ person team
- Open sourceLive
Liquid Finance
Personal finance PWA with AI receipt scanning, multi-currency budgets and full offline capability. The one I actually use every week, which is the only honest test of a personal-finance app.
- React
- Supabase
- Vite
- Netlify
- PrivateLive
ThumbSnap AI
Generative design SaaS for thumbnails. Took a job that ran two hours of designer time and made it thirty seconds, the clearest example on this list of what changes when specification is the only bottleneck.
- Generative AI
- SaaS
- Design automation
- PrivateLive
Safar
E-visa eligibility checker for Pakistani, Bangladeshi and Nigerian passport holders, with coverage expanding. Built because the existing answer to "can I travel there" was twelve browser tabs and a forum post from 2019.
- Travel
- Eligibility engine
- Product
- Open sourceRunning
Autonomous Article Writer
A publishing pipeline that ships 15+ articles a day at zero operational cost. It is also the automation layer behind the newsletter further up this page: the reference implementation, not a demo.
- Automation
- n8n
- Publishing
Tools
The stack I actually pay for.
Short list on purpose. I review things I use on real work, and I say when something is not worth it: a directory where everything scores well is an advert, not a review.
Some links below are affiliate links, marked as such. If you buy through one I may earn a commission at no extra cost to you. It does not affect the rating: I have left tools I was offered money to include off this list entirely.
[PLACEHOLDER: Tool 1 name]
[PLACEHOLDER: category, e.g. Coding]
[PLACEHOLDER: rating out of 5]
[PLACEHOLDER: Your one-line verdict]
Use it when — [PLACEHOLDER: The specific situation this is the right pick for]
[PLACEHOLDER: Tool 2 name]
[PLACEHOLDER: category, e.g. Writing]
[PLACEHOLDER: rating out of 5]
[PLACEHOLDER: Your one-line verdict]
Use it when — [PLACEHOLDER: The specific situation this is the right pick for]
[PLACEHOLDER: Tool 3 name]
[PLACEHOLDER: category, e.g. Images]
[PLACEHOLDER: rating out of 5]
[PLACEHOLDER: Your one-line verdict]
Use it when — [PLACEHOLDER: The specific situation this is the right pick for]
[PLACEHOLDER: Tool 4 name]
[PLACEHOLDER: category, e.g. Automation]
[PLACEHOLDER: rating out of 5]
[PLACEHOLDER: Your one-line verdict]
Use it when — [PLACEHOLDER: The specific situation this is the right pick for]
Watch
The whole argument, out loud.
If you would rather watch than read, start here. Screen share included, so you see the actual specifications rather than slides about them.
- [PLACEHOLDER: YouTube video ID]
[PLACEHOLDER: Video 1 title]
[PLACEHOLDER: e.g. 12:04][PLACEHOLDER: One line on what this video covers]
- [PLACEHOLDER: YouTube video ID]
[PLACEHOLDER: Video 2 title]
[PLACEHOLDER: e.g. 24:30][PLACEHOLDER: One line on what this video covers]
Nothing loads from YouTube until you press play. No cookies are set before that.
Listen
The podcast.
Longer conversations with people who built things they were not qualified to build.
- 01[PLACEHOLDER: Episode 1 title][PLACEHOLDER: e.g. 48 min][PLACEHOLDER: Guest, and what they built]
- 02[PLACEHOLDER: Episode 2 title][PLACEHOLDER: e.g. 52 min][PLACEHOLDER: Guest, and what they built]
- 03[PLACEHOLDER: Episode 3 title][PLACEHOLDER: e.g. 41 min][PLACEHOLDER: Guest, and what they built]
[PLACEHOLDER: where it is published: Spotify, Apple, YouTube]
Writing
Longer arguments, worked through properly.
Where the newsletter is what happened this week, these are the pieces I keep sending people.
[PLACEHOLDER: category] · [PLACEHOLDER: e.g. 9 min]
[PLACEHOLDER: Article 1 title]
[PLACEHOLDER: Two-line excerpt]
Read[PLACEHOLDER: category] · [PLACEHOLDER: e.g. 6 min]
[PLACEHOLDER: Article 2 title]
[PLACEHOLDER: Two-line excerpt]
Read[PLACEHOLDER: category] · [PLACEHOLDER: e.g. 12 min]
[PLACEHOLDER: Article 3 title]
[PLACEHOLDER: Two-line excerpt]
Read
Before you book
The objections, answered honestly.
I tried this. It wrote code I had to throw away.
I am not technical. Is this actually for me?
My engineers will hate this.
I do not have time to learn a new system right now.
Why you? There are a hundred AI consultants now.
What if it does not work for us?
Last thing
The call is free and I am not going to pitch you.
Thirty minutes. You describe what you are trying to ship and where it is stuck, I tell you what I would do about it. If a sprint is the right answer I will say so. If it is not, I will say that too: most of these calls end with somebody getting a useful answer and not spending any money, and that is a completely fine outcome for me.
P.S. If you only take one thing from this page, take this: the next time you get bad output, do not rewrite the prompt. Write the brief you would have handed a contractor who cannot ask you questions. The difference will be obvious inside an hour, and you will not need to hire anybody to see it.