Forward-deployed designer · 2 of 5 slots booked

You vibe coded the first version. I'll work with you to design and build it with AI.

I join your team for two-week sprints, forward deployed. I design, build in real code and make the launch video. A live link every Friday.

US$1,800 per 2-week sprint. Stop after any sprint.

  • Led design and product at Aampe, acquired by MoEngage
  • Co-founded Nocoloco and HueGrid
  • 15 tools live on Tiny Design Shop
Label Buddy at Aampe, from idea to MVP in one week.

Built for and with

  • Aampe
  • Framer
  • Lendingkart
  • Plum
  • Scapia
  • Townhall

How it works

Week one turns your brief into one clear goal. Every Friday after that, you get something you can click.

A tangled line labelled Ambiguity straightens into a clear line labelled Clarity, with 4 steps along it: Book and brief, Week 1 · Clarity, Build weeks, Launch week.01 Book and brief02 Week 1 · Clarity03 Build weeks04 Launch weekAmbiguityClarity A tangled line labelled Ambiguity straightens into a clear line labelled Clarity, with 4 steps along it: Book and brief, Week 1 · Clarity, Build weeks, Launch week.01 Book and brief02 Week 1 · Clarity03 Build weeks04 Launch weekAmbiguityClarity
  1. 01

    Before sprint 1

    Book and brief

    We talk for 30 minutes. You send what you have: the repo, the feature list, a few references.

  2. 02

    Sprint 1, week 1

    Week 1 · Clarity

    I sit in your channels and your repo, and turn the messy brief into one goal, a one-page plan and a working prototype. By Friday you know what to build and why.

  3. 03

    Week 2 onward

    Build weeks

    I build next to you. Each Monday we agree one goal, preview links land every two days, and Friday brings a live link and a Loom.

  4. 04

    The last week

    Launch week

    I record the walkthroughs from the real build and render the launch video. You launch with the content done.

A build week

  1. MonGoal call
  2. TueBuild
  3. WedPreview link
  4. ThuPolish
  5. FriLive link and Loom

What clients say

What I've designed and built

Most of it at Aampe, where I led design and product. Each card opens the full story.

At Aampe · Head of Design & Product

Label Buddy's QA review, with the review queue approved and the summary ready Case study · Aampe Label Buddy Label QA for 100k+ copy lines. Mohana proved the idea in onboarding; I turned it into an eight-stage pipeline and shipped the MVP in a week. 1 weekidea to MVP40 hours to 1 hourof QA a month per CS member15revisions in that week Read the case study

For clients · Nocoloco and HueGrid

My own products

Going from idea to product communication

The docs that ship with the product, and the launch videos that announce it.

Product docs

Launch videos

Every video here is a web page with a clock. I wrote my taste into the harness once, so a launch video starts from one prompt. Tap a tile to hear it.

The prompt

Make a 17 second launch video for Responsive Preview. Hook on the problem, show it at three widths, end on the install line.
That's the whole brief I give the harness.
Responsive Preview launch17s · 16:9 · Remotion
Seats reel, for a workshop25s · 4:5 · LinkedIn
Aampe case study reel2 min · 16:9 · HTML
Builder Course announcement29s · 4:5 · LinkedIn
m2 intro sting7s · 16:9 · Reused
Same launch, cut square17s · 1:1 · Cut-down
Agentic Brand Assets launch1:04 · 16:9 · HTML
m2 outro sting8s · 16:9 · Reused

How a prompt becomes a launch video

My thought process, the way I'd sketch it on paper. The loop back from my notes is the part that keeps the videos mine.

How a prompt becomes a launch video: A prompt, then My rules, then Scenes on a clock, then Stills ok?, then Render, then Sound, then QA gate, then Ship. If the stills are not right, my notes go back to the scenes.my gomy notesUI changed? edit a lineA promptone paragraph, in plain wordsMy rulespalette, pace, de-slop, tasteScenes on a clockreel.html · seek(t)Stills ok?RenderPlaywright frames → ffmpegSoundCuelume cue on every beatQA gatelength, decode, −18 LUFSShipMP4, square cut, web encodeShared kit· woven texture· NaN Jaune + Onest· 17 Cuelume sounds· m2 stingsmy taste, written down oncesame HTML, same frames,every timerenders are slow,so I approvestills firstchange it once, every reel gets it How a prompt becomes a launch video: A prompt, then My rules, then Scenes on a clock, then Stills ok?, then Render, then Sound, then QA gate, then Ship. If the stills are not right, my notes go back to the scenes.my gomy notesA promptone paragraph, in plain wordsMy rulespalette, pace, de-slop, tasteScenes on a clockreel.html · seek(t)Stills ok?RenderPlaywright frames → ffmpegSoundCuelume cue on every beatQA gatelength, decode, −18 LUFSShipMP4, square cut, web encodeShared kit· woven texture· NaN Jaune + Onest· 17 Cuelume sounds· m2 stings
  • my taste, written down once
  • same HTML, same frames, every time
  • renders are slow, so I approve stills first
  • change it once, every reel gets it

The harness, in the open

Book a 30-min call

US$1,800 per 2-week sprint · 2 of 5 slots booked

Taking new builds now · 2 of 5 slots booked

Work with me

Book 30 minutes and talk me through your brief. I'll tell you what week one would ship.

Madhuri Maram

Madhuri Maram

A brief, and what week one would ship

  • 30 minutes
  • Google Meet, link sent on booking
  • Remote, times shown in your time zone

We could cover

  1. Your brief and who it's for
  2. What's built already, if anything
  3. What week one would ship

Pick a day

See open times

Two weeks at a time

US$1,800/ 2 weeks

Every Friday you get

  • A live link to the real product, in your repo
  • A Loom of what changed and why
  • One product at a time. Stop after any sprint. You own everything.
  • Next week's plan, and at each sprint's end, the call to continue or stop

In launch week

The launch video, plus square and vertical cuts for your feed.

Why two weeks

At Aampe I built tools straight from one customer's problem, next to a forward-deployed engineer. Two weeks is long enough to ship something real and short enough that you never lose a month. And it's just me, so nothing gets lost in a handoff.

Questions

What does forward deployed mean here?

I join your team for the sprint: your repo, your Slack or Linear, your standup if you have one. I make product and design calls with you, then build them. No brief handed to an agency.

What if I want changes?

Tell me on the Friday Loom. Changes become next week's goal. Between Fridays I make the calls, so the sprint stays on track.

What do you need from me?

The repo or what you've built, access to it, and a short brief. The sprint starts when I have all three.

Can you pick up a product I've already vibe coded?

Yes, and most briefs start there. I read what exists, keep what works, and tell you what I'd rebuild and why before I touch it.

How much gets done in a sprint?

We agree one goal each Monday, and I push the product as far toward it as the week allows. You get two weeks of senior work on what matters most, not a fixed list.

Do I own the work?

Yes, all of it: the code and the video source files. I may show it on my site unless you'd rather I didn't.

Can I stop?

Yes, at the end of any sprint. No notice needed.

Do you only do the build, or only the launch video?

Either works. The two together save the most time, because the recordings come straight from a build I already know.

I need an ongoing design partner.

Happy to discuss a longer engagement, shaped around what you need. Here's how my fractional work runs.

Which time zone do you work in?

I work remotely and async by default. At Aampe I worked with teams in San Francisco and Singapore, so overlapping with your hours is routine.

My stack

Grouped by step. If your team uses something else, I'll work in yours.

PlanBriefs, priorities, the roadmap

  • Linear
  • Notion
  • Claude Cowork

DesignFlows, systems, high-fidelity screens

  • Figma
  • Framer

BuildWorking software, in your repo or a new one

  • Claude Code
  • Codex
  • Cursor
  • Replit
  • Lovable

MotionLaunch videos rendered from code

  • Remotion
  • Playwright
  • ffmpeg
  • Cuelume

ShipPreviews, hosting, releases

  • GitHub
  • Vercel
  • Cloudflare

No-codeFrom the Nocoloco years

  • Framer
  • Webflow
  • Glide

More work

The rest of my Aampe work. Each one opens the full story.