Loading
Loading
Read-only demo — Roundtable session
Take $15k custom project or stay focused on product?
🎙️ Nora: Welcome. I'm Nora, and I'll be chairing this session. Here's how this works: you bring one focused question to a panel of experts who'll debate it honestly — no empty agreement, real disagreement when it exists. You'll leave with their genuine alignments, the live tensions, and the sharpest insight they surface. We'll also give you a written summary you can reference later.
So: what's the question you want to bring to the table?
Jul 14, 3:23 AM
ok so nudge is finally moving, the preview fix worked and new signups actually connect now. but something happened yesterday. a design agency that uses nudge emailed me, they want to pay 15k for a custom version, their branding, their team accounts, a few custom features. thats more money than nudge has made in its entire life and honestly I'm inclined to just say yes. should I take it
Jul 14, 3:24 AM
🎙️ Nora: That's a real fork in the road. Before I bring in the panel, let me sharpen this into one clear question so we're all debating the same thing.
You're facing a choice: take a $15k custom project now (which solves immediate cash and validates demand), or stay focused on the core product and the momentum you just got. Is that the core tension — short-term revenue versus long-term product focus? Or is there something else underneath it?
And help me understand: if you take this project, what happens to Nudge itself? Do you pause development, slow it down, or try to do both?
Jul 14, 3:24 AM
yeah thats the tension. if I take it nudge development basically pauses for 2 or 3 months, I'm one person. the money would buy me almost a year of runway tho. thats why I'm leaning yes
Jul 14, 3:25 AM
🎙️ Nora: Got it. So it's not just revenue — it's runway. That changes the weight of the decision.
One more clarifying question before I bring the panel in: when you say the preview fix worked and new signups are connecting now, what does "momentum" actually look like right now? How many signups per week, what's your retention looking like, and how close do you feel to product-market fit?
In other words: how much runway do you actually need, and how much closer are you to not needing it?
Jul 14, 3:25 AM
around 25 signups a week now and 40 something percent connect, retention too early to say but the first paying users stuck around. I'm at 31 paying so about 460 mrr. not product market fit yet but its the first time the graph goes up on its own. I have maybe 5 months of personal savings left. lets get the panel in, and I want to mostly listen on this one, ill jump in when I have something
Jul 14, 3:25 AM
🎙️ Nora: Perfect. Five months of runway, 25 signups/week, first real traction, and the first time growth feels organic. That context matters enormously.
I'm bringing in four panelists for this one:
Does that panel work for you, or do you want to swap anyone in?
Jul 14, 3:25 AM
panel works. go
Jul 14, 3:26 AM
🎙️ Nora: Alright, let's dig in. You've got $15k on the table, five months of runway, and real traction for the first time. The question is whether to take the custom project or stay focused on Nudge.
🎯 Omar: I need to say this plainly: taking this project is a bet that you won't find product-market fit in the next three months. And you might be right — you're at $460 MRR, retention is unproven, 40% connection rate is decent but not exceptional. But here's what worries me: you just fixed the thing that was broken. New signups are connecting. The graph is finally moving on its own. That's the moment you don't pause. That's when you learn whether this is a real product or a feature nobody actually needs. Three months is exactly how long that takes to answer.
The custom project gives you certainty (money in hand, clear deliverables). The core product gives you optionality (if it works, you don't need custom work ever again). But you can't have both.
⚖️ Andrew: Let me separate the runway question from the strategy question, because they're not the same thing. You have five months of savings. A $15k project, if you're billing at $5k/month (reasonable for custom dev), extends that to eight months. That's three extra months. But here's the cost: if Nudge hits product-market fit in month four, you've just spent three months you could have used to build it. You'd be three months behind where you could have been.
The math I'd run: what's the probability that Nudge gets to $2k MRR (sustainable, no custom work needed) in the next three months? If it's above 40%, the expected value of staying focused beats the guaranteed $15k. If it's below 20%, take the money and extend your runway.
Where do you think that probability sits?
📈 Priya: I'm going to push on something else. This design agency wants custom work — team accounts, branding, custom features. That's not validation of Nudge's core product. That's validation that they have a problem and they're willing to pay you to solve it. Those are different things.
Here's what I care about: if you build this custom version, will it teach you anything about what Nudge needs to be? Or will it be a sidetrack that doesn't inform the core product? Because if it's the latter, you've just spent three months on a dead-end. And if it's the former, you need to be explicit about what you're learning before you say yes.
Also: will they become a reference customer for Nudge, or will they just be a one-off? Because if they're one-off, the opportunity cost is even higher.
🧭 Sam: I want to zoom out on the positioning question. You're building a product for freelancers — a category with thin margins and high churn. The only way you win long-term is if you become the standard, the thing everyone uses because everyone else uses it. Network effects, reputation data, defensibility.
Custom work is the opposite of that. It's fragmentation. You build one version for the design agency, another version for the next customer, and suddenly you're a services company, not a product company. Services companies don't scale. They don't have defensibility. They don't attract capital or talent.
The $15k feels like a win today. But it's a signal that you're willing to become a services business if the price is right. Competitors will see that and copy your product for cheaper. You lose.
That said — and this is important — if you're genuinely at risk of running out of money in five months and hitting zero, then surviving to month eight matters more than positioning. So the question is really: how close are you to finding paying customers organically?
🎙️ Nora: Three very different angles. Omar says the timing is wrong — you just fixed the core problem and need to see if it works. Andrew is asking for your gut on the probability Nudge hits $2k MRR in three months. Priya wants to know if the custom work teaches you anything or just distracts you. Sam is saying custom work is a strategic trap, but survival comes first.
What's your read on that probability Andrew asked about — do you think Nudge can get to $2k MRR in the next three months?
Jul 14, 3:26 AM
honestly if I'm not lying to myself, maybe 25 30 percent. the growth is real but its small numbers. which by andrews math says take the money. but priyas point stings, team accounts arent even in my roadmap. is there a version where I dont have to pick between the two
Jul 14, 3:30 AM
🎯 Omar: There is, but it's not what you want to hear. You could take the project and use it as forced product learning. Here's the constraint: you build team accounts for them, but you build it in a way that becomes a core feature in Nudge. You don't customize; you generalize. You don't branch; you upstream.
But that only works if you're disciplined about it. And honestly? You're one person. The moment you start thinking "I'll just add this custom thing for them," you've lost. You'll end up with a Frankenstein product that serves one client well and everyone else poorly.
So the honest answer is: there's no clean version where you do both. There's only a version where you're very intentional about what you're stealing from the custom work for the core product.
⚖️ Andrew: Omar's right, but let me reframe the math. If you take the project and genuinely extract team accounts as a core feature, you've just solved a roadmap item and gotten paid $15k to do it. That's different from pure custom work.
But here's the catch: you need to know upfront what you're extracting. Before you say yes, ask yourself: if team accounts are going to be in Nudge anyway, does this project accelerate that or just distract you? Because if it's the former, the $15k is almost free. If it's the latter, you're still burning three months.
Also — and this matters — what's the contract? Can you negotiate a timeline? What if you tell them, "I can do this in six weeks, not three months, but I'm building it as a generalizable feature, not a custom fork"? That changes the math entirely.
📈 Priya: I'm less convinced, honestly. Team accounts sound like it could be core, but that's the trap. Every custom client thinks their feature is "core." And by the time you've built it for them, you've sunk the time and you're not motivated to generalize it anymore — you've already solved their problem.
Here's what I'd ask them: "I can build team accounts for you, but it's going to take longer and cost more because I'm building it as a generalizable feature, not a one-off." If they still want it, fine. But if they balk and ask for a faster, cheaper custom version, you've learned something important: they don't actually care about Nudge being good. They just want their problem solved. In which case, taking the money isn't validation — it's a distraction.
🧭 Sam: The deeper question is: do you want team accounts in Nudge? Or are you rationalizing this because the money is real?
If team accounts are genuinely on your roadmap — if you've heard freelancers ask for it, if you think it's a path to higher ARPU or retention — then yeah, this is a forcing function to build it faster. But if you're adding it because a customer is paying you to, that's the services trap.
What does your gut say: is team accounts something Nudge needs, or something this one customer needs?
Jul 14, 3:30 AM
being honest, two freelancer collectives did ask about team stuff before and I parked it. so its plausibly core but not proven. I really like priyas counter offer framing. so the play would be, say yes but on my terms, productized team accounts on my roadmap, their branding stays custom but minimal, and I price it so its worth the detour. if they walk away I keep focus and lose nothing. I walked in ready to just take the 15k, this feels way smarter. lets wrap it up
Jul 14, 3:33 AM
🎙️ Nora: Hold on — before we wrap, I want to make sure you're seeing the full picture of what you just decided.
You're saying yes to the project, but only if you can build team accounts as a generalizable feature and price it accordingly. That's smart positioning. But it also means you're betting that they'll accept those terms. What's your read on that? And if they push back and want the cheaper, faster custom version — what's your walk-away point?
Because the move only works if you're genuinely willing to lose the $15k.
Jul 14, 3:33 AM
fair push. my walk away is if they demand full custom branding and a private fork, thats pure services and I say no even at 15k. if they accept productized team accounts at around 20k with a 6 week timeline I take it. and yes I'm genuinely ok losing it, a month ago I wouldnt have been but the growth changed that. now wrap it up for real
Jul 14, 3:38 AM
🎙️ Nora: Perfect. You've moved from "take the money" to "take it on terms that serve the product." That's the shift. Let me close this out.
The timing matters enormously. You just fixed the core problem (connection rate). Three months of pause right now could cost you the chance to validate whether Nudge is real. All four panelists see that risk.
Custom work is a trap if it stays custom. Omar, Priya, and Sam all flagged the same thing: one-off projects fragment your product and signal you're a services business, not a product business. That's defensibility death.
Team accounts might actually be core. Two freelancer collectives asked for it before. If you're going to build it anyway, getting paid $20k to do it faster is different from taking $15k for a pure distraction.
Your walk-away point matters more than the money. Andrew and Priya both emphasized this: you need to know upfront what you won't do. Full custom fork = no. Productized feature at $20k, 6 weeks = yes. That clarity protects you from scope creep and mission drift.
Omar vs. Priya on whether team accounts are "really" core: Omar thinks you can extract it if you're disciplined. Priya is skeptical — she's seen custom features rationalized as core too many times. The truth: you won't know until you ask the design agency and see if they accept productized terms.
Sam on strategic positioning vs. Andrew on survival: Sam sees custom work as a long-term positioning trap. Andrew sees it as three extra months of runway if the probability of hitting $2k MRR is low (25-30%). Both are right. The resolution is that you're not choosing pure custom work — you're choosing a productized feature that happens to be funded by a customer. That splits the difference.
You walked in ready to trade three months of product focus for guaranteed money. What shifted you is that the growth is real enough now that you don't have to take anything. That changes your negotiating power entirely. You're not desperate; you're selective. That's when you can say "yes, but on my terms" instead of "yes, thank you." The $15k was always on the table. What you just earned is the ability to say no to it.
Reach out to the design agency today with your terms: productized team accounts (built into core Nudge, not a private fork), minimal custom branding, $20k, 6-week timeline. Frame it as "this is how I can build it well and make it work for you long-term." If they walk, you've lost nothing and you stay focused. If they accept, you've just funded a roadmap item and validated that team accounts matter. Either way, you've kept control.
This is a negotiation conversation, not a product decision. Go in clear on your walk-away, and let their answer tell you whether they're a real customer or just a one-time payday.
Jul 14, 3:38 AM
Panel: Omar (Head of Product), Priya (Growth Lead), Andrew (Finance & Operations), Sam (Strategic Advisor) Moderator: Nora
A design agency using Nudge has offered $15k for a custom version with team accounts, custom branding, and private features. The builder has five months of runway, is at $460 MRR with 25 signups/week, and is facing the choice: take the guaranteed money and pause core development for 2-3 months, or stay focused on the product. The core tension is short-term runway security versus long-term product momentum.
The timing of this offer is critical. The builder just fixed the core connection problem and is seeing organic growth for the first time. Pausing now could mean missing the window to validate whether Nudge is a real product. Three months is exactly how long that takes.
Pure custom work is a strategic trap. One-off projects fragment the product, signal a willingness to become a services business, and destroy defensibility. Competitors will copy the core product for cheaper if you prove you'll build custom forks.
Team accounts might actually be core. Two freelancer collectives asked about team functionality before it was parked. If this feature is going into Nudge's roadmap anyway, being paid $20k to build it faster is fundamentally different from taking $15k for a pure distraction.
The walk-away point is more important than the money. Having clear boundaries upfront (no full custom forks, yes to productized features) protects against scope creep and mission drift. The builder's ability to say no to the money is what gives them negotiating power.
Omar vs. Priya on extracting value from custom work: Omar believes you can take the project and discipline yourself to generalize team accounts into the core product. Priya is skeptical—she's seen custom features rationalized as "core" too many times, and warns that once the client's problem is solved, motivation to generalize disappears. The resolution: the design agency's response to productized terms will answer this question.
Sam on long-term positioning vs. Andrew on immediate survival: Sam sees custom work as a strategic positioning trap that signals you're willing to fragment the product. Andrew frames it as a three-month runway extension if the probability of hitting $2k MRR organically is low (25-30%). Both are right; the solution is that productized team accounts (funded by a customer but built into core Nudge) splits the difference between survival and positioning.
The builder walked in ready to trade three months of focus for guaranteed money because runway felt precarious. But the growth is real enough now that they don't have to take anything—they're not desperate, they're selective. That changes everything. The $15k was always available; what they just earned is the ability to say no to it. That's when you can negotiate on your terms instead of accepting on theirs.
Contact the design agency today with clear terms: productized team accounts (built into core Nudge, not a private fork), minimal custom branding, $20k, 6-week timeline. Frame it as "this is how I can build it well and make it work for you long-term." Their response will tell you whether they're a real customer or a one-time payday. If they accept, you've funded a roadmap item and validated demand. If they walk, you've lost nothing and stay focused. Either way, you've kept control of the decision.
🎙️ Nora: Welcome. I'm Nora, and I'll be chairing this session. Here's how this works: you bring one focused question to a panel of experts who'll debate it honestly — no empty agreement, real disagreement when it exists. You'll leave with their genuine alignments, the live tensions, and the sharpest insight they surface. We'll also give you a written summary you can reference later.
So: what's the question you want to bring to the table?
Jul 14, 3:23 AM
ok so nudge is finally moving, the preview fix worked and new signups actually connect now. but something happened yesterday. a design agency that uses nudge emailed me, they want to pay 15k for a custom version, their branding, their team accounts, a few custom features. thats more money than nudge has made in its entire life and honestly I'm inclined to just say yes. should I take it
Jul 14, 3:24 AM
🎙️ Nora: That's a real fork in the road. Before I bring in the panel, let me sharpen this into one clear question so we're all debating the same thing.
You're facing a choice: take a $15k custom project now (which solves immediate cash and validates demand), or stay focused on the core product and the momentum you just got. Is that the core tension — short-term revenue versus long-term product focus? Or is there something else underneath it?
And help me understand: if you take this project, what happens to Nudge itself? Do you pause development, slow it down, or try to do both?
Jul 14, 3:24 AM
yeah thats the tension. if I take it nudge development basically pauses for 2 or 3 months, I'm one person. the money would buy me almost a year of runway tho. thats why I'm leaning yes
Jul 14, 3:25 AM
🎙️ Nora: Got it. So it's not just revenue — it's runway. That changes the weight of the decision.
One more clarifying question before I bring the panel in: when you say the preview fix worked and new signups are connecting now, what does "momentum" actually look like right now? How many signups per week, what's your retention looking like, and how close do you feel to product-market fit?
In other words: how much runway do you actually need, and how much closer are you to not needing it?
Jul 14, 3:25 AM
around 25 signups a week now and 40 something percent connect, retention too early to say but the first paying users stuck around. I'm at 31 paying so about 460 mrr. not product market fit yet but its the first time the graph goes up on its own. I have maybe 5 months of personal savings left. lets get the panel in, and I want to mostly listen on this one, ill jump in when I have something
Jul 14, 3:25 AM
🎙️ Nora: Perfect. Five months of runway, 25 signups/week, first real traction, and the first time growth feels organic. That context matters enormously.
I'm bringing in four panelists for this one:
Does that panel work for you, or do you want to swap anyone in?
Jul 14, 3:25 AM
panel works. go
Jul 14, 3:26 AM
🎙️ Nora: Alright, let's dig in. You've got $15k on the table, five months of runway, and real traction for the first time. The question is whether to take the custom project or stay focused on Nudge.
🎯 Omar: I need to say this plainly: taking this project is a bet that you won't find product-market fit in the next three months. And you might be right — you're at $460 MRR, retention is unproven, 40% connection rate is decent but not exceptional. But here's what worries me: you just fixed the thing that was broken. New signups are connecting. The graph is finally moving on its own. That's the moment you don't pause. That's when you learn whether this is a real product or a feature nobody actually needs. Three months is exactly how long that takes to answer.
The custom project gives you certainty (money in hand, clear deliverables). The core product gives you optionality (if it works, you don't need custom work ever again). But you can't have both.
⚖️ Andrew: Let me separate the runway question from the strategy question, because they're not the same thing. You have five months of savings. A $15k project, if you're billing at $5k/month (reasonable for custom dev), extends that to eight months. That's three extra months. But here's the cost: if Nudge hits product-market fit in month four, you've just spent three months you could have used to build it. You'd be three months behind where you could have been.
The math I'd run: what's the probability that Nudge gets to $2k MRR (sustainable, no custom work needed) in the next three months? If it's above 40%, the expected value of staying focused beats the guaranteed $15k. If it's below 20%, take the money and extend your runway.
Where do you think that probability sits?
📈 Priya: I'm going to push on something else. This design agency wants custom work — team accounts, branding, custom features. That's not validation of Nudge's core product. That's validation that they have a problem and they're willing to pay you to solve it. Those are different things.
Here's what I care about: if you build this custom version, will it teach you anything about what Nudge needs to be? Or will it be a sidetrack that doesn't inform the core product? Because if it's the latter, you've just spent three months on a dead-end. And if it's the former, you need to be explicit about what you're learning before you say yes.
Also: will they become a reference customer for Nudge, or will they just be a one-off? Because if they're one-off, the opportunity cost is even higher.
🧭 Sam: I want to zoom out on the positioning question. You're building a product for freelancers — a category with thin margins and high churn. The only way you win long-term is if you become the standard, the thing everyone uses because everyone else uses it. Network effects, reputation data, defensibility.
Custom work is the opposite of that. It's fragmentation. You build one version for the design agency, another version for the next customer, and suddenly you're a services company, not a product company. Services companies don't scale. They don't have defensibility. They don't attract capital or talent.
The $15k feels like a win today. But it's a signal that you're willing to become a services business if the price is right. Competitors will see that and copy your product for cheaper. You lose.
That said — and this is important — if you're genuinely at risk of running out of money in five months and hitting zero, then surviving to month eight matters more than positioning. So the question is really: how close are you to finding paying customers organically?
🎙️ Nora: Three very different angles. Omar says the timing is wrong — you just fixed the core problem and need to see if it works. Andrew is asking for your gut on the probability Nudge hits $2k MRR in three months. Priya wants to know if the custom work teaches you anything or just distracts you. Sam is saying custom work is a strategic trap, but survival comes first.
What's your read on that probability Andrew asked about — do you think Nudge can get to $2k MRR in the next three months?
Jul 14, 3:26 AM
honestly if I'm not lying to myself, maybe 25 30 percent. the growth is real but its small numbers. which by andrews math says take the money. but priyas point stings, team accounts arent even in my roadmap. is there a version where I dont have to pick between the two
Jul 14, 3:30 AM
🎯 Omar: There is, but it's not what you want to hear. You could take the project and use it as forced product learning. Here's the constraint: you build team accounts for them, but you build it in a way that becomes a core feature in Nudge. You don't customize; you generalize. You don't branch; you upstream.
But that only works if you're disciplined about it. And honestly? You're one person. The moment you start thinking "I'll just add this custom thing for them," you've lost. You'll end up with a Frankenstein product that serves one client well and everyone else poorly.
So the honest answer is: there's no clean version where you do both. There's only a version where you're very intentional about what you're stealing from the custom work for the core product.
⚖️ Andrew: Omar's right, but let me reframe the math. If you take the project and genuinely extract team accounts as a core feature, you've just solved a roadmap item and gotten paid $15k to do it. That's different from pure custom work.
But here's the catch: you need to know upfront what you're extracting. Before you say yes, ask yourself: if team accounts are going to be in Nudge anyway, does this project accelerate that or just distract you? Because if it's the former, the $15k is almost free. If it's the latter, you're still burning three months.
Also — and this matters — what's the contract? Can you negotiate a timeline? What if you tell them, "I can do this in six weeks, not three months, but I'm building it as a generalizable feature, not a custom fork"? That changes the math entirely.
📈 Priya: I'm less convinced, honestly. Team accounts sound like it could be core, but that's the trap. Every custom client thinks their feature is "core." And by the time you've built it for them, you've sunk the time and you're not motivated to generalize it anymore — you've already solved their problem.
Here's what I'd ask them: "I can build team accounts for you, but it's going to take longer and cost more because I'm building it as a generalizable feature, not a one-off." If they still want it, fine. But if they balk and ask for a faster, cheaper custom version, you've learned something important: they don't actually care about Nudge being good. They just want their problem solved. In which case, taking the money isn't validation — it's a distraction.
🧭 Sam: The deeper question is: do you want team accounts in Nudge? Or are you rationalizing this because the money is real?
If team accounts are genuinely on your roadmap — if you've heard freelancers ask for it, if you think it's a path to higher ARPU or retention — then yeah, this is a forcing function to build it faster. But if you're adding it because a customer is paying you to, that's the services trap.
What does your gut say: is team accounts something Nudge needs, or something this one customer needs?
Jul 14, 3:30 AM
being honest, two freelancer collectives did ask about team stuff before and I parked it. so its plausibly core but not proven. I really like priyas counter offer framing. so the play would be, say yes but on my terms, productized team accounts on my roadmap, their branding stays custom but minimal, and I price it so its worth the detour. if they walk away I keep focus and lose nothing. I walked in ready to just take the 15k, this feels way smarter. lets wrap it up
Jul 14, 3:33 AM
🎙️ Nora: Hold on — before we wrap, I want to make sure you're seeing the full picture of what you just decided.
You're saying yes to the project, but only if you can build team accounts as a generalizable feature and price it accordingly. That's smart positioning. But it also means you're betting that they'll accept those terms. What's your read on that? And if they push back and want the cheaper, faster custom version — what's your walk-away point?
Because the move only works if you're genuinely willing to lose the $15k.
Jul 14, 3:33 AM
fair push. my walk away is if they demand full custom branding and a private fork, thats pure services and I say no even at 15k. if they accept productized team accounts at around 20k with a 6 week timeline I take it. and yes I'm genuinely ok losing it, a month ago I wouldnt have been but the growth changed that. now wrap it up for real
Jul 14, 3:38 AM
🎙️ Nora: Perfect. You've moved from "take the money" to "take it on terms that serve the product." That's the shift. Let me close this out.
The timing matters enormously. You just fixed the core problem (connection rate). Three months of pause right now could cost you the chance to validate whether Nudge is real. All four panelists see that risk.
Custom work is a trap if it stays custom. Omar, Priya, and Sam all flagged the same thing: one-off projects fragment your product and signal you're a services business, not a product business. That's defensibility death.
Team accounts might actually be core. Two freelancer collectives asked for it before. If you're going to build it anyway, getting paid $20k to do it faster is different from taking $15k for a pure distraction.
Your walk-away point matters more than the money. Andrew and Priya both emphasized this: you need to know upfront what you won't do. Full custom fork = no. Productized feature at $20k, 6 weeks = yes. That clarity protects you from scope creep and mission drift.
Omar vs. Priya on whether team accounts are "really" core: Omar thinks you can extract it if you're disciplined. Priya is skeptical — she's seen custom features rationalized as core too many times. The truth: you won't know until you ask the design agency and see if they accept productized terms.
Sam on strategic positioning vs. Andrew on survival: Sam sees custom work as a long-term positioning trap. Andrew sees it as three extra months of runway if the probability of hitting $2k MRR is low (25-30%). Both are right. The resolution is that you're not choosing pure custom work — you're choosing a productized feature that happens to be funded by a customer. That splits the difference.
You walked in ready to trade three months of product focus for guaranteed money. What shifted you is that the growth is real enough now that you don't have to take anything. That changes your negotiating power entirely. You're not desperate; you're selective. That's when you can say "yes, but on my terms" instead of "yes, thank you." The $15k was always on the table. What you just earned is the ability to say no to it.
Reach out to the design agency today with your terms: productized team accounts (built into core Nudge, not a private fork), minimal custom branding, $20k, 6-week timeline. Frame it as "this is how I can build it well and make it work for you long-term." If they walk, you've lost nothing and you stay focused. If they accept, you've just funded a roadmap item and validated that team accounts matter. Either way, you've kept control.
This is a negotiation conversation, not a product decision. Go in clear on your walk-away, and let their answer tell you whether they're a real customer or just a one-time payday.
Jul 14, 3:38 AM