Open to product and project roles

Hello,

Harsh here!

Product and project manager who designs and builds

Email me

About me

Harsh Upadhyay, product and project manager, designer and builder

The Verde Form site open on a laptop resting on an olive green sofa

Harsh Upadhyay

Send me a message

You can send me a message here, or email harshmartinez@gmail.com

Harsh Upadhyay

Send me a message

You can send me a message here, or email harshmartinez@gmail.com

[ ON THIS PAGE ]

Send me a message

Capability

Process

The Result

Tools

Availability

FAQ

I don’t just design the product,
I run the project that ships it.

[ CAPABILITIES ]

Project delivery, end to end

I take a brief with no boundary around it and turn it into a dated plan with an owner on every line, then I run it to the date.

Product management

I decide what gets built and what waits, I write the requirements the build runs on, and I own what version one is allowed to be.

Design, and the system behind it

I take a product from the first flows to the shipped screens, and I keep the design system honest as the team grows.

The build, in Framer and Shopify

I build and launch the thing myself rather than hand it over, and I set up the CMS, the integrations, the automation and the email behind it.

The RankFrame plugin panel showing an image SEO score and the pages it audited

PROJECT DELIVERY, END TO END

Project delivery, end to end

I take a brief with no boundary around it and turn it into a dated plan with an owner on every line, then I run it to the date.

Product management

I decide what gets built and what waits, I write the requirements the build runs on, and I own what version one is allowed to be.

Design, and the system behind it

I take a product from the first flows to the shipped screens, and I keep the design system honest as the team grows.

The build, in Framer and Shopify

I build and launch the thing myself rather than hand it over, and I set up the CMS, the integrations, the automation and the email behind it.

A product screen and the notes that shaped it

A process rooted in
clarity and cuts.

[ WORK PROCESS ]

Project delivery

Product management

Design and systems

No-code build

Scope it and agree it

Turn the brief into a numbered list of decisions, each with an owner and a date, agreed in writing.

Plan it and sequence it

Break the work down, put it in order, and name the risks early.

Design it and build it

Design the screens and the states, prototype what needs feeling, and build what I can myself.

Ship it and report on it

Ship to the date, then one written update a week: shipped, next, need from you, at risk.

What was in the way

What I did about it

No privacy policy or terms at launch

Drafted both, flagged the open questions, and held go live until they were answered.

Analytics loading before consent

Made the tag manager conditional on consent, as PECR requires.

Community posts with no moderation

Kept moderation inside V1 rather than deferring it.

Scope wider than the fixed launch date

Cut to a UK only V1, with an owner against every deferred item.

CMS cost that did not suit their scale

Moved to a custom web CMS, keeping the editing model.

Account deletion with no grace period

Added a grace window, so a mis-tap is recoverable.

Project delivery

Product management

Design and systems

No-code build

Scope it and agree it

Turn the brief into a numbered list of decisions, each with an owner and a date, agreed in writing.

Plan it and sequence it

Break the work down, put it in order, and name the risks early.

Design it and build it

Design the screens and the states, prototype what needs feeling, and build what I can myself.

Ship it and report on it

Ship to the date, then one written update a week: shipped, next, need from you, at risk.

No privacy policy or terms at launch

Drafted both, flagged the open questions, and held go live until they were answered.

Analytics loading before consent

Made the tag manager conditional on consent, as PECR requires.

Community posts with no moderation

Kept moderation inside V1 rather than deferring it.

Scope wider than the fixed launch date

Cut to a UK only V1, with an owner against every deferred item.

CMS cost that did not suit their scale

Moved to a custom web CMS, keeping the editing model.

Account deletion with no grace period

Added a grace window, so a mis-tap is recoverable.

Scope it and agree it

I turn the brief into a numbered list of decisions, each with an owner and a date, and get it agreed in writing before anything is drawn.

Plan it and sequence it

I break the work down, put it in order, name the risks early, and say out loud when two of the things we want cannot both be true.

Design it and build it

I design the screens and the states, prototype what needs feeling, and build what I can myself rather than hand over a file to interpret.

Ship it and report on it

I ship to the date, then write one update a week in the same four parts: shipped, next, need from you, and at risk.

What was in the way, and what I did

No privacy policy or terms at launch

Drafted both, flagged the open questions, and held go live until they were answered.

Analytics loading before consent

Made the tag manager conditional on consent, as PECR requires.

Community posts with no moderation

Kept moderation inside V1 rather than deferring it.

Scope wider than the fixed launch date

Cut to a UK only V1, with an owner against every deferred item.

CMS cost that did not suit their scale

Moved to a custom web CMS, keeping the editing model.

Account deletion with no grace period

Added a grace window, so a mis-tap is recoverable.

Scope it and agree it

I turn the brief into a numbered list of decisions, each with an owner and a date, and get it agreed in writing before anything is drawn.

Plan it and sequence it

I break the work down, put it in order, name the risks early, and say out loud when two of the things we want cannot both be true.

Design it and build it

I design the screens and the states, prototype what needs feeling, and build what I can myself rather than hand over a file to interpret.

Ship it and report on it

I ship to the date, then write one update a week in the same four parts: shipped, next, need from you, and at risk.

What was in the way, and what I did

No privacy policy or terms at launch

Drafted both, flagged the open questions, and held go live until they were answered.

Analytics loading before consent

Made the tag manager conditional on consent, as PECR requires.

Community posts with no moderation

Kept moderation inside V1 rather than deferring it.

Scope wider than the fixed launch date

Cut to a UK only V1, with an owner against every deferred item.

CMS cost that did not suit their scale

Moved to a custom web CMS, keeping the editing model.

Account deletion with no grace period

Added a grace window, so a mis-tap is recoverable.

Every product starts as a decision, not a screen. Most of the work happens before Figma opens, in the scope, the plan and the things we agree not to build.

See Study Case

Essor

A wealth app for people who had never felt welcome in one.

See Study Case

DadWell

Thirteen open blockers, one shippable V1.

See Study Case

Tixoo

A date that could not move, so the scope did.

See Study Case

RankFrame

The SEO tool Framer did not have.

Four Framer components on the Marketplace, Infinite Story, Slider Studio, Editorial CMS Strip and Depth Wave Gallery, each with a copy button

See Study Case

Component library

A component library run as a product, not a portfolio.

See Study Case

Solika Arts

One system, four portals, because one screen served nobody.

See Study Case

Varxity

A storefront that costs the same next year as it does this year.

See Study Case

Form

A shop with a point of view was wearing a template.

See Study Case

ProEd

Twenty seven course pages, and one template behind all of them.

The tools I actually
build in.

✳

Each one earns its place, from the first flows through to the thing that ships. Together they are how a small team moves quickly without losing the thread.

I design and build in the same week, so the tools on the left and the tools on the right are the same set.

Things you might want to know

[ FREQUENTLY ASKED QUESTIONS ]

How do you run a project from start to finish?

I scope it first, which means turning the brief into a numbered list of decisions with an owner and a date against each one, agreed in writing. Then I sequence the work, name the risks early, and design and build it. I report once a week in the same four parts, so nobody has to ask where it is.