I'm Suhag. I own the technical side, and the outcome.
I build the technical side of B2B SaaS products, and I stay responsible for it. Founders bring me in at different points: some for a first version, some to grow a product that is already working, some to take pressure off a team that is stretched. What stays the same is that I own the outcome.
Work I can point to.
Built solo from zero to production. Millions of US carrier records indexed, sub-second ranked search, Stripe subscription billing across 4 plans. Next.js, PostgreSQL, Prisma.
READ THE CASE STUDY →Straining at ~2M users on shared hosting. I moved it onto real infrastructure: Nginx, load balancing, multiple instances, automated CI/CD. It now serves millions of users a month at 99.99% uptime. Mobile load time went from 5.3s to 2.3s, and the API is about 40% faster.
READ THE CASE STUDY →Core engineer on the first version of Labthunder, a SaaS that later raised EUR 500K (after I had left). Then senior full-stack developer, shipping features and reviewing the team's PRs.
How I think about the work.
Boring stack, exciting product.
The founders who hire me aren't paying for my technology choices - they're paying for working software, on time, that their team can extend after I hand it off. That means I reach for Next.js, Postgres, Stripe, and Resend before I reach for anything novel. Boring tools have solved error messages, boring tools have StackOverflow threads at 2 a.m., boring tools still work three years later when the original engineer is gone.
I stay current. I use Cursor and Claude every day. But "current" means "understands the new tools deeply enough to know when not to use them."
Ship weekly or it isn't real.
A codebase that hasn't been deployed in two weeks is a theory. Every engagement I run has a weekly delivery rhythm: a working URL, a changelog, a short Loom, a question for the founder. This isn't process theatre - it's the only reliable way to surface scope drift before it becomes a crisis.
I've worked with founders who had never seen their product deployed until week six of a twelve-week engagement. By then it's too late to discover the architecture doesn't match the business model. Weekly ships make that impossible.
The codebase is the company's asset.
I write code as if I'm handing it off the day it's finished. Named functions, explicit types, zero magic. No clever one-liners that save three tokens and cost an hour of onboarding. No private abstractions that only make sense to me.
This is partly professional pride and partly pragmatic: founders who get a codebase they can actually read are the ones who refer the next client. Every referral in my backlog came from a founder who said some version of "I actually understand what he built."
Same desk. Different decade.
Textile engineering first. Then code.
I studied textile engineering, then taught myself to code from YouTube in 2019, in Tangail, Bangladesh.
First paying client.
Landed my first paying client and learned the lesson I still work by: I optimize for what works for paying customers, not what looks clever in a tutorial.
Production scale.
Shipped products across SaaS, e-commerce, and content for founders in the US, UK, EU, and AU. Earned a CS degree along the way.
AI in production.
Added RAG pipelines, LLM features, and evals to the stack, built with the same production standards as everything else.
150+ shipped. Focused on B2B SaaS.
Building new SaaS products, growing live ones, and taking pressure off stretched teams. 100+ founders worked with.
Not just code.
Documenting consumer pain points across 10 sectors in Bangladesh. Curiosity project slowly becoming a side business.
Daily experiments with Claude, Gemini, Veo 3, NotebookLM. The experiments inform the work.
Same town, same desk. Walking distance to my parents.
What founders say. In their words.
Suhag delivered a production-ready SaaS in 7 weeks - auth, billing, the works. I've hired a lot of engineers and this is the first handoff where I actually understand the codebase.
★★★★★ · Founder, US-based SaaS startup
We had a Lovable prototype that was falling apart in testing. Suhag took it to production in three weeks. Stripe is working, auth is solid, and the code is clean. 100% recommend.
★★★★★ · Co-founder, AI startup (UK)
Best engineer I've worked with remotely. Weekly Looms, honest about scope, never missed a deadline. The code he writes looks like he's planning to work with it for years.
★★★★★ · CTO, Series-A company (AU)
Suhag Al Amin is a full-stack engineer based in Tangail, Bangladesh, who owns the technical side for B2B SaaS founders and teams in the United States, United Kingdom, European Union, and Australia. He builds, scales, and maintains SaaS products with Next.js, React, Node, and Python. He built his own B2B SaaS, Carrier Intelligence, solo from zero to production, and moved a UK music platform onto infrastructure that now serves millions of users a month at 99.99% uptime. He has shipped 150+ products and worked with 100+ founders over 6+ years. Every engagement starts with a one-week Technical Assessment. Services: Technical Assessment (from $400), SaaS Engineering Partnership (from $2,500/month), SaaS Product Build (from $4,500), AI Prototype Rescue (from $400), AI Development (from $3,000), Full-Stack Web Development (from $400). Inquiries: suhag.alamin13@gmail.com or https://cal.com/suhag/intro-call.
Find me.
TANGAIL, BANGLADESH · GMT+6 · FLEXIBLE HOURS
If you are building, growing, or maintaining a B2B SaaS product and want a straight read on the technical side, book an intro call.
Book an intro callSend a messageDOWNLOAD RESUME (PDF)