Every product I've shipped,
specced like one.

Problem

Social media agencies send creative and captions to clients for approval over WhatsApp and email threads — which makes "what exactly did the client approve" a real liability question, not a rhetorical one. A verbal or checkbox approval breaks the moment a caption gets edited after the fact. Clients also won't create an account just to review a post.

Approach

Wrote the product PRD, then a 39-section Technical Requirements Doc translating it into a concrete engineering baseline — stack, data model, security, and a core invariant: approval is never a mutable boolean. Every decision binds to an exact, immutable creative + caption version; editing either after approval doesn't quietly update the record, it invalidates it and requires re-approval. Paired this with a full Design System v2.0 (57 Figma frames across agency desktop, mobile client review, and onboarding) and a 10-day engineering alpha plan sequencing auth → content batching → guest review links → versioning/invalidation → annotations → hardening.

Outcome

Engineering handover baseline complete: PRD, 39-section TRD, and 57-frame design system, ready for build. Guest reviewers need no account — a capability-scoped link is the entire client-side surface. Currently in active development against the 10-day alpha plan.

Problem

CAT exam prep is generic: every student gets the same mock test and the same syllabus order, and institutes see the aggregate score, not why a student is actually stuck.

Approach

Own the product end-to-end: diagnostic assessments, adaptive practice journeys, recommendation logic, PRDs, and a responsible-AI and data-consent framework, running B2C and B2B tracks in parallel.

Outcome

In beta-launch planning and iteration. No inflated numbers here: that's the honest state of a beta.

Problem

An early-stage founder's office needed growth execution and product-adjacent judgment, with no dedicated team to provide either. Every deliverable had to be usable immediately, not iterated on for weeks.

Approach

Owned pitch decks, branding decks, and campaign creatives; ran SEO and Google Ads; and audited website UX with specific, actionable recommendations that fed directly into product and content decisions, reading the site the way a PM reads a product, not just a marketer looking for conversion copy.

Outcome

Directly shaped brand and growth decisions inside a lean founding team during a formative stretch of the company.

Problem

A large-scale startup ecosystem event needed product-launch-level rigor, not just event logistics.

Approach

Owned the full lifecycle (partnerships, planning, and execution) for an event convening 65+ startups, 25+ VC firms, and 1,000+ participants.

Outcome

Delivered on time: a genuine multi-stakeholder rollout under real deadline pressure.

Problem

SMBs needed credible digital media work without the cost of hiring an in-house team: a gap between "hire one freelancer" and "hire a full agency."

Approach

Analyzed market trends to define which service offerings would actually sell, then productized them into repeatable packages instead of bespoke one-offs, as a two-person founding team owning positioning, go-to-market, and client acquisition from day one.

Outcome

Built the business from zero to a functioning client roster.