As a non-technical founder what should I be doing while the product is developed?

I still remember sitting in a co-working space in 2014, watching my co-founder demolish the keyboard like he was racing in a typing competition. I had no idea what half the variable names meant, but I did know one thing: if I kept staring at the IDE, both of us would go insane. That was the moment I realised the “non-technical” label isn’t a handicap—it’s the entire outside world the product has to survive in.

If you’re in that spot now—waiting on builds, pull-requests, and the occasional “it works on my machine” shrug—don’t hover behind the devs. There’s plenty that only you can push forward (and a few traps you can spring if you’re not careful).

Business development first. Calendar-block coffees, cold DMs, small conferences, the awkward breakfast meetup at 7 a.m.—all of it. Aim for a running list of potential design partners and pilot customers; ten decent conversations beat a hundred spray-and-pray intros every time. I’m not entirely sure this scales past Series A, but in the early days your face is the brand, so show up.

Next comes fundraising—and budgeting. Yes, polish the deck, rehearse the story, but also crack open a spreadsheet and sanity-check pricing for the tools you’re eyeing. More than once I’ve seen founders commit to an expensive analytics suite before they had a single paying customer (guilty as charged). Negotiate starter tiers, defer annual plans, keep the burn flexible—you’ll thank yourself when a term sheet slips by a quarter.

Marketing & branding isn’t just a logo sprint. People want to click something tangible, so spin up an interactive demo with Navattic or similar and let sales run wild without begging engineering for a sandbox. While you’re at it, write the positioning doc in plain English—if you can’t explain the product in one sentence to your aunt, the market won’t bother either.

Then, customer development. Book Zoom calls, send personal Loom recordings, meet the two beta users who actually replied and watch them fumble through the prototype. Record everything (well, more like the meaningful bits—nobody wants a 90-minute file that never gets re-watched). Patterns emerge shockingly fast once you shut up and listen.

Product management is where you bridge those calls and the backlog. Sit with the devs, decide which three metrics matter this quarter, and instrument only those. Collect-everything analytics feels powerful until you’re drowning in events you can’t query without BigQuery. And if you’re evaluating no-code add-ons like Pendo or Freshpaint, loop engineers in early—one stray CSS selector change can nuke a month of tracking (ask me how I know).

Team & culture. Energy is the currency here. Don’t be that ghost. Show progress every week, celebrate quick wins, spot burnout before it lands. Hire for attitude over résumé; skills are teachable, apathy isn’t.

You’ll notice none of this requires committing a single line of code, yet every task bends the trajectory of the product. Some weeks you’ll feel like you’re herding cats, other weeks you’ll swear nothing is moving. That wobble is normal; just keep nudging the flywheel and trust compound interest to kick in.

Have fun out there—the software can’t sell itself, and the market won’t wait.