Startup Technical Advisor

Sometimes you don’t need another engineer — you need a startup technical advisor: a senior person who has built and led before, on call a few hours a month to keep you from expensive mistakes. I’m Kuldeep Pisda, a former startup CTO and DjangoCon / EuroPython speaker based in Bengaluru.

What I advise on#

• Architecture reviews — a second set of eyes on the design before you commit months to it, with the scaling and security concerns named early.
• Hiring and team — writing role specs, sitting in on senior interviews, and sanity-checking your first engineering hires so you don’t over- or under-hire.
• Technical due diligence — for founders or investors: an honest read on a codebase, its risks, and what it’ll take to scale or maintain.
• Roadmap and trade-offs — what to build now, what to defer, and where the “clever” shortcut will cost you later.
• Postgres and Django deep-dives — when a specific problem needs someone who’s actually solved it before.

Why an advisor beats a full hire (sometimes)#

Early on, the highest-leverage technical input is a few good decisions, not more hours of code. An experienced advisor catches the architecture mistake, the risky migration, or the wrong hire before it’s expensive — for a fraction of the cost of a senior full-timer. When you genuinely need hands-on leadership, that’s a fractional CTO conversation instead.

Experience behind the advice#

Good advice is usually the smallest intervention that works, and two published write-ups show how I apply that. When a serverless platform couldn’t hold the stateful SFTP session one partner integration needed, I didn’t fight the platform or containerize the codebase — I carved out one tiny single-job Node sidecar and kept every scrap of business logic on the other side of that boundary. And sometimes the smallest intervention is none: I once shipped a 1.2 GB course video without fixing it — measured the pain first, then deliberately deferred the transcoding pipeline, because premature infrastructure kills young products faster than rough edges do. That instinct — escape hatch over rewrite, defer over gold-plate — is what you’re buying by the hour. Behind it sit 6+ years of Django and PostgreSQL systems, a platform scaled past 30,000 users, founding-SRE and SOC 2 work, and time as a startup CTO; the case studies show the reasoning.

How it works#

Usually a light monthly retainer — a standing call plus async access for the questions that come up between them. Remote, IST, comfortable with US and EU hours.

FAQ#

How much time is this? Typically a few hours a month — a regular call plus async questions. Flexible around what you need.

What does it cost? The advisory retainer is $2,000/month — two 60-minute calls per month plus async review of up to 4 design docs or PRs. A one-off second opinion on a specific decision is $500: one 90-minute call and a written recommendation within 48 hours. When a deep read of the codebase is warranted, an audit is $4,000 — ranked written findings in 7 calendar days plus a walkthrough call, credited toward any retainer or build started within 60 days. All prices in USD plus GST where applicable, in writing before we start.

Can you do a one-off review or due diligence? Yes — a fixed-scope architecture review or a code/tech due-diligence report is a common starting point.

Do you advise investors too? Yes — technical due diligence on a target company is something I do for both founders and investors.

What if we need hands-on help after? Then we scale up to fractional or project work. Advising is often how that starts.

Advisor or fractional CTO? Advisor is lighter-touch guidance; fractional CTO is ongoing hands-on ownership. See fractional CTO for startups.

Let’s talk#

Tell me where you’d want a second opinion — get in touch, or grab a time below:

Related: Fractional CTO for Startups · Technical Co-Founder for Startups · Hire a Fractional CTO in India · Hire a Django Consultant