Time-budgeted outline assuming 60 minutes. Adjust for your actual time.
Pre-call (5 min before):
Have ready in front of you: comp framing email you sent Varin, the cap table summary numbers (8% TBA, 61/10/15 founder split, 12M post, 3M target, 18-month runway), the thermal memo (summarized), and the Lora process status. Don’t read from notes. Have them as backup.
Open (3-5 min): Frame the call and your decision.
“I’m in late-stage negotiation for fractional-to-full CTO at a pre-seed consumer hardware startup, and I’m in parallel process for Head of Engineering at a more established startup. I have to make decisions in the next 2-3 weeks. Want your help on three buckets: (1) deal mechanics on the CTO offer, (2) technical and execution risk at the company, (3) how I think about parallel processes and timing. I’ll go in that order, you push back wherever. We have about an hour.”
This sets scope, signals you’ve done your thinking, and gives him explicit permission to challenge.
Bucket 1 — Deal mechanics (15-20 min):
Start here because it’s the most concrete and gets him oriented to your situation. Cover in this order:
-
Cap table and equity sizing. Brief the structure: 8% promised but not yet issued, coming from CEO’s 61% share. Three operating founders are full-time no-salary (CEO 61%, CPO 10% + 10% on full-time, COO 15%). You’d be salaried-founder. Question: “Does this read as appropriate equity for late-arriving CTO at this stage given the founder structure? Where would you push?”
-
Comp. 12-15K fractional and full CTO, scaling to market at “first institutional close.” Question: “I’ve agreed to this in principle as 30-50% of market for pre-seed. The trigger language for scaling is undefined. How would you structure that trigger to protect against indefinite below-market comp?”
-
Acceleration and termination protection. Question: “What acceleration terms did you negotiate at Rokt, and what would you do differently? What termination-without-cause protections should I be asking for?”
-
Refresh grants vs. anti-dilution. Question: “Anti-dilution at the founder level raised flags from a previous CEO. I’ve reframed around refresh grants at financing events and pro-rata rights. Is that the right substitution?”
-
Founder-investing-alongside. Question: “You invested into Rokt when you joined. Walk me through the decision and whether you’d do it again at pre-seed hardware specifically. How did you size it?”
This is the bucket where his pattern recognition is most directly useful. Get his unvarnished view.
dont sound like an employee moving a company is really hard. executive have a lot of liability 8% is actually really good, kind of a red flag tbh. diluted at a flat rate. accelerated vest. should exercise, but doesn’t always work out. start thinking like a founder/executive, not an employee hard to hire hardware engineers lean on recruiters. ask about contractor why are they leaving make sure no one is committing fraud. it’s a good sign that no one is getting paid ask about triggers. know the table, know the burn, know the terms who’s makign decisions really know the advisors, how are they being compensated dgaf attitude. corey didn’t even look at the offer, but he was in a diff financial situation. don’t take promises, take things in writing they wont renogiate, take things in writing be very careful about getting sucked into accelerated vest, unless the shares are a penny QSBS tax exemption always an option, only if shares are a penny, and 5k. Seed will create a valuation and FMV that might make it impossible to do that. no one cares what you do. sounds risky. asking ppl to leave jobs in a tough market, to join unstable/unknown company. need to put on a strong, confident that this company knows whats they’re doing, there are no problems hardware engineers dont like risk, get paid like shit. making existing team work might be the move, and then worry about hiring ios/android engineers. lock this in, be done with it.
Lora is an easier sell rn according to Corey. chill job, easy to hire ios devs. ppl love that kind of product. if things were to accelerate quickly, give corey a call. if Pync gets their shit together, then you can start to think about investment. raise a big seed 4-5. hardware moves slow, margins are on hardware. when someone freaks out, it shows. and it propagates to everyone else. it could also be a great opportunity. you have to be a rock, everyone you work with will see your nervous system. killer offer actually protect yourself, keep an eye for yourself. you’re in for the long haul, probably going down with the shop. corey knew he was cooked at rokt and stayed on bc he was a shithead lol you need to be 100% locked in and engaged even more at the top CTO level if you the job right, the job is ez, it’s the politics and the scrapping, branding is the main job corey offers to be a sounding board in the future, keep him posted what i end up doing.
Bucket 2 — Technical and execution risk (20-25 min):
Heavier bucket. Two sub-topics.
2a. Hardware and product execution risk:
Brief him: “Product is BLE collar + WiFi dock + iOS/Android + on-device ML on Apollo3. 30 collars on dogs in Thailand currently. July launch targeted in 3 months. No CTO in seat. Firmware built by lowest-bid Chinese contractor. CPO is finance background, no consumer hardware. No qualified hardware advisor.”
Then the specific issue: “I’ve identified what I believe is a thermal safety defect — sustained LTE transmission heats the shell above 40°C against pet skin. Proposed software mitigation addresses wrong root cause. I’ve drafted a memo recommending dropping LTE from v1.”
Questions:
- “How do you read the risk profile here? Is this ‘normal pre-seed hardware chaos that gets fixed’ or is this ‘CEO judgment shown by the absence of qualified technical leadership for 12+ months’?”
- “How should an incoming CTO engage with safety-critical defects in the trial period? Send the memo now, hold until formal engagement, or use it as a Phase 2 entry condition?”
- “What’s the right way to surface this to the CEO without it reading as overreach?”
2b. Burn, runway, and Series A path:
Brief: “Burn modeled at 1.55M against 1M from Singapore. Burn assumes 210-220K base plus me at full CTO breaks that average.”
Questions:
- “At this burn and runway, what’s a realistic Series A timeline? Is 14-16 months from pre-seed close achievable for a hardware company that may need to remediate before scaling?”
- “If pre-seed underfills at, say, 3M, how does my position change?”
- “What would you want to see in Phase 2 deliverables to be confident Phase 3 actually happens?”
This is where he’s most useful because he’s run the playbook of “incoming senior technical leader walks into a company with technical debt and timeline pressure.” Let him talk.
Bucket 3 — Parallel processes and timing (10-15 min):
Brief: “I have a Head of Engineering process at a more established startup — better funded, traction, revenue. Three rounds in. CEO touch-base done. Spotify-advisor technical round pending. I haven’t told them about Pync. Financial pressure is real — bookstore, no green card, wife is US citizen, Thai E2 visa with my own LLC.”
Questions:
- “How do I think about Pync vs. the other role given my financial situation and visa constraints?”
- “What signals would tell you to take Pync vs. walk?”
- “How would you handle the parallel processes — keep both alive until offers, or commit early?”
Don’t lead him toward a preferred answer. His unprompted lean is the signal.
Close (5 min): Action items and the offer.
Three actions you want from him:
-
Followup question or clarification if he wants more detail on anything before forming a view. Offer to send him the rough numbers (not the file) or the thermal memo (under understanding that it’s confidential pre-NDA work product).
-
Ongoing availability. “If I proceed with Pync, would you be willing to stay engaged as informal advisor through Phase 2 entry? I’d want to come back to you at a couple of decision points.”
-
Direct ask. “What would you do in my position?” Save this for last. Forces him to commit to a view, not just provide framing.
What you don’t bring up:
- NDA terms, governing law mechanics, trust equity structure — these are counsel questions.
- Specific compensation numbers from Lora — you don’t have them yet, and bringing them up is premature.
- Detailed CPO equity grievances — you’ve corrected your read, and litigating his stake with Corey is a poor use of his time.
- Founder-character analysis of Varin — Corey hasn’t met her, his pattern recognition is on technical and structural items, not interpersonal read.
Tone calibration:
You’re asking for his judgment. Don’t argue with it during the call. If he says something you disagree with, note it and move on. Process it after. Mentors disengage when they feel their advice is being relitigated in real time. Save your pushback for a followup if needed.
One discipline:
You have a tendency in our conversation to circle back to themes (CPO equity, CEO judgment) when new information has already addressed them. Don’t do that with Corey. He’s giving you 60 minutes. Each topic gets one pass. If you want more on something, schedule another call. Tight loop, clear asks, exit.