Founder Sales Email Sequence: Win Deals With Authenticity, Not Tricks

In the early days, you are the sales team. There's no SDR to warm up leads, no AE to close deals, no sales engineer to handle technical questions. It's just you, sending emails between writing code and fixing bugs.
This is actually a superpower, not a burden.
Founder-led sales emails convert better than polished sales sequences because they're real. Prospects can tell when an email comes from someone who built the product versus someone paid to sell it. The authenticity gap is enormous, and it works in your favor.
But authenticity doesn't mean winging it. You still need structure. You still need follow-up. You still need templates you can adapt quickly without reinventing every email from scratch.
This guide provides founder-specific sales email sequences: first outreach, follow-ups, demo requests, proposal follow-through, and everything in between. These templates work because they sound like a founder wrote them, not like they came from a sales playbook. If you are looking for a broader overview of startup email priorities, our startup email sequence guide covers what to build first when resources are limited.
Why Founder Sales Emails Are Different
Traditional sales email advice doesn't work for founders. Here's why:
| Sales Rep Emails | Founder Emails |
|---|---|
| "I'd love to show you our platform" | "I built this because I had the same problem" |
| Focus on product features | Focus on the problem and your journey |
| Polished and professional | Real and sometimes rough |
| Sequential playbook | Adaptive conversation |
| Volume over quality | Quality over volume |
When a sales rep sends an email, prospects think "another pitch." When a founder sends an email, prospects think "the person who built this reached out personally." That difference matters.
The goal isn't to seem like a founder. It's to be one. Your emails should reflect the direct, problem-focused, sometimes imperfect reality of early-stage building.
The Founder Sales Mindset
Before we get to templates, understand the mindset:
-
You're not selling. You're having a conversation. Early customers become partners. You're looking for people who want to build something together.
-
Rejection means refinement, not failure. Every "no" or ignored email teaches you something about your positioning or your market.
-
Time is your scarcest resource. Every email should be worth sending. Don't blast 1,000 generic emails. Send 50 thoughtful ones.
-
Your story is your differentiator. Why you built this, what you learned, what keeps you up at night. That's what separates you from funded competitors.
-
Follow up without apology. Following up isn't annoying when you have something valuable to offer. It's a service.
First Outreach: Making Initial Contact
The first email has one job: get a response. Not a demo, not a sale. Just a response that opens a conversation.
All Email Sequence Templates
The Founder Story
Use case: When your story resonates with the prospect's situation
Description: Leading with your personal journey
Subject line: Building something for [their problem]
Hi [firstName], I'm [yourName], founder of [productName]. I'm reaching out personally because I think you might face a problem I know well. Before starting [productName], I [your relevant experience]. The thing that drove me crazy was [specific problem]. I tried [solutions you attempted], but nothing really worked. So I built [productName]. It [core value proposition in one sentence]. I noticed [Their Company] is [observation about their situation]. I'm curious if [problem] is something you deal with too. Would you be open to a quick call? Even if [productName] isn't a fit, I'd love to learn about how you're handling this. Your perspective would help me build better. [yourName] Founder, [productName] P.S. Here's a 2-minute demo if you'd rather see than read: [demoLink]
The Specific Observation
Use case: When you have genuine insight into their situation
Description: Starting with something you noticed about them
Subject line: Noticed [specific thing] at [Their Company]
Hi [firstName], I saw that [Their Company] just [specific observation: launched feature, hired role, announced news]. Congrats on [specific achievement]. When companies hit this stage, they usually start dealing with [problem you solve]. At least, that's what happened to me when I was [your relevant experience]. I built [productName] to solve exactly this. In short, it [one-sentence value prop]. Not sure if this is on your radar yet. If it is, I'd love to show you what we've built. If not, no worries, but I'm curious what you're using instead. Either way, happy to chat. [yourName] Founder, [productName]
The Mutual Connection
Use case: When you have a warm intro or mutual connection
Description: Leveraging a shared relationship
Subject line: [Mutual connection] suggested I reach out
Hi [firstName], [Mutual connection] mentioned you've been dealing with [problem]. They thought you might want to hear about what I'm building. I'm [yourName], founder of [productName]. We help [target customer type] with [specific problem]. [Mutual connection] has been using it for [timeframe], and they thought it might be relevant for [Their Company]. The quick version: [productName] lets you [key benefit]. Most customers see [specific result] within [timeframe]. Would you have 20 minutes this week to chat? I'd love to hear about your situation and see if there's a fit. [yourName] P.S. Tell [mutual connection] I owe them a coffee for the intro.
The Direct Ask
Use case: For busy prospects who prefer brevity
Description: No fluff, straight to the point
Subject line: Quick question about [their problem area]
Hi [firstName], Quick question: is [specific problem] something [Their Company] is actively trying to solve? I'm building [productName], which helps [target customer type] with this exact issue. We've helped companies like [similar company] achieve [specific result]. If this is a priority, I'd love to share what we've learned. If not, no worries at all. [yourName] Founder, [productName]
The Thought Leadership Hook
Use case: When you have relevant content to share
Description: Leading with valuable content
Subject line: Wrote this after talking to [X] [role] about [problem]
Hi [firstName], I've spent the last few months talking to [role]s about [problem]. The patterns were so consistent I wrote them up: [link to content] The TL;DR: most teams are [common mistake], when they should be [better approach]. Given what [Their Company] is doing with [relevant initiative], I thought this might resonate. If you have thoughts after reading, I'd love to hear them. And if you're actively working on this problem, I built [productName] to help. Happy to show you what we've learned. [yourName] Founder, [productName]
Leading with your personal journey
Building something for [their problem]
Hi [firstName],
I'm [yourName], founder of [productName]. I'm reaching out personally because I think you might face a problem I know well.
Before starting [productName], I [your relevant experience]. The thing that drove me crazy was [specific problem]. I tried [solutions you attempted], but nothing really worked.
So I built [productName]. It [core value proposition in one sentence].
I noticed [Their Company] is [observation about their situation]. I'm curious if [problem] is something you deal with too.
Would you be open to a quick call? Even if [productName] isn't a fit, I'd love to learn about how you're handling this. Your perspective would help me build better.
[yourName] Founder, [productName]
P.S. Here's a 2-minute demo if you'd rather see than read: [demoLink]
Follow-Up Sequence: Persistence Without Annoyance
Most deals happen after the first email. But most founders give up too early. Here's how to follow up without being that annoying sales person. For more detailed follow-up frameworks, our email follow-up sequence guide covers timing and tone escalation in depth.
Follow-Up 1: Add Value (Day 3-4)
All Email Sequence Templates
The Value Add
Use case: Default first follow-up
Description: Following up with something useful
Subject line: Re: [original subject]
Hi [firstName], Following up on my note from a few days ago. Not trying to be pushy, just wanted to add something useful. I put together [resource: guide, checklist, framework] on [relevant topic] based on what I've learned building [productName]. Thought it might be relevant for [Their Company]: [link] The section on [specific part] might be especially useful given [what you know about their situation]. Still happy to chat about [problem] if you're interested. Otherwise, hope the resource helps. [yourName]
The New Angle
Use case: When first email may have missed the mark
Description: Approaching from a different direction
Subject line: Different question
Hi [firstName], I reached out last week about [productName]. No worries if it wasn't relevant. I'm trying a different angle: what's the biggest headache in your [department/area] right now? I ask because I've talked to a lot of [role]s at [company type], and there are usually 2-3 problems that come up constantly. I'm curious if your experience matches. Even if it's not something [productName] helps with, I'd love to learn. Happy to share what I've heard from others in exchange. [yourName]
The Case Study
Use case: When you have a relevant customer story
Description: Sharing relevant customer success
Subject line: How [Similar Company] solved [problem]
Hi [firstName], Quick follow-up with something I thought you'd find interesting. [Similar Company] was dealing with [problem] pretty badly. They tried [what they tried before] but nothing stuck. After implementing [productName], they [specific result]. Here's the quick version of what they did: [link or brief summary] The reason I mention it: [Similar Company] is similar to [Their Company] in [specific way]. The same approach might work for you. Worth a conversation? [yourName]
The Direct Check-In
Use case: For prospects who prefer directness
Description: Simple, honest follow-up
Subject line: Still on your radar?
Hi [firstName], Just checking in on my note from last week about [productName]. I know you're busy. If [problem] isn't a priority right now, no worries. But if you're interested and just haven't had time to respond, I'm happy to work around your schedule. Let me know either way? [yourName]
Following up with something useful
Re: [original subject]
Hi [firstName],
Following up on my note from a few days ago. Not trying to be pushy, just wanted to add something useful.
I put together [resource: guide, checklist, framework] on [relevant topic] based on what I've learned building [productName]. Thought it might be relevant for [Their Company]: [link]
The section on [specific part] might be especially useful given [what you know about their situation].
Still happy to chat about [problem] if you're interested. Otherwise, hope the resource helps.
[yourName]
Follow-Up 2: Different Medium (Day 7-8)
All Email Sequence Templates
The Video Follow-Up
Use case: When text isn't breaking through
Description: Offering a different format
Subject line: 60-second video for you
Hi [firstName], I've sent a couple emails. Rather than send another wall of text, I recorded a quick video: [loomLink] It's 60 seconds. Shows exactly what [productName] does and why I think it might help [Their Company]. If you watch it and have questions, just reply. If you watch it and it's not relevant, no problem. Either way, wanted to try a different approach. [yourName]
The Phone Option
Use case: When email may not be their preferred channel
Description: Offering a call instead of email
Subject line: Would a call be easier?
Hi [firstName], I've sent a couple emails about [productName]. Maybe email isn't the best way to reach you. Would a quick call be easier? I promise to keep it short. If so, here's my calendar: [calendarLink] Or just reply with a time that works and I'll make it happen. If you'd rather not chat, no hard feelings. Just let me know and I'll stop following up. [yourName]
The LinkedIn Mention
Use case: Multi-channel approach
Description: Referencing other channels
Subject line: Tried LinkedIn too
Hi [firstName], I sent you a connection request on LinkedIn too, just in case that's easier. No need to accept if you'd rather not. I'm genuinely just trying to find the best way to reach you about [problem]. If you're dealing with it, I think [productName] could help. If you're not, or if this isn't the right time, I'd love to know so I can focus elsewhere. Appreciate any response, even a "not interested." [yourName]
Offering a different format
60-second video for you
Hi [firstName],
I've sent a couple emails. Rather than send another wall of text, I recorded a quick video: [loomLink]
It's 60 seconds. Shows exactly what [productName] does and why I think it might help [Their Company].
If you watch it and have questions, just reply. If you watch it and it's not relevant, no problem.
Either way, wanted to try a different approach.
[yourName]
Follow-Up 3: The Break-Up (Day 14-21)
All Email Sequence Templates
The Honest Close
Use case: Default break-up email
Description: Respectful final follow-up
Subject line: Should I close the loop?
Hi [firstName], I've reached out a few times about [productName]. Since I haven't heard back, I'm guessing either: 1. You're interested but timing is off 2. You're not interested (totally fine) 3. My emails are going to spam If it's #1, just tell me when to follow up and I will. If it's #2, no hard feelings. I'll stop reaching out. If it's #3, check your spam folder? Either way, I appreciate your time. [yourName] Founder, [productName]
The Door Left Open
Use case: When you want to preserve the relationship
Description: Ending without pressure
Subject line: Last one from me (for now)
Hi [firstName], This is my last follow-up about [productName]. I don't want to be that founder who won't take a hint. If [problem] ever becomes a priority, or if you want to chat about [industry/topic] in general, my door is open. Just reply to this thread. Wishing you and [Their Company] the best. [yourName]
The Future Value
Use case: Exit with value
Description: Leaving with something useful
Subject line: Closing the loop + something useful
Hi [firstName], I'm going to stop following up, but I wanted to leave you with something useful regardless of whether we ever work together. Here's [resource you created] about [relevant topic]: [link] It's based on what I've learned from [number] customers/conversations. The section on [specific part] is probably most relevant for [Their Company]. If you ever want to chat about [problem] or [productName], you know where to find me. [yourName]
Respectful final follow-up
Should I close the loop?
Hi [firstName],
I've reached out a few times about [productName]. Since I haven't heard back, I'm guessing either:
- You're interested but timing is off
- You're not interested (totally fine)
- My emails are going to spam
If it's #1, just tell me when to follow up and I will.
If it's #2, no hard feelings. I'll stop reaching out.
If it's #3, check your spam folder?
Either way, I appreciate your time.
[yourName] Founder, [productName]
Post-Demo Follow-Up: Moving Toward Close
After a demo, the dynamics change. They've seen your product. They've met you. Now you need to keep momentum without being pushy.
All Email Sequence Templates
Same Day Recap
Use case: Send within hours of demo
Description: Immediate post-demo follow-up
Subject line: Thanks for the call + next steps
Hi [firstName], Thanks for taking the time to chat today. I enjoyed learning about [specific thing they mentioned]. Here's a quick recap of what we discussed: **Your situation:** [their problem/challenge] **How [productName] helps:** [relevant solution points] **Next steps:** [what you agreed to] As promised, I'm attaching [whatever you promised: pricing, case study, trial access, etc.]. A few things I forgot to mention: - [Additional point 1] - [Additional point 2] If questions come up as you're reviewing, just reply to this email. I'm also happy to loop in [team member] if you want to go deeper on [technical topic]. Talk soon. [yourName]
Stakeholder Summary
Use case: When they need to get buy-in
Description: Summary for prospect to share internally
Subject line: Summary for your team (easy to forward)
Hi [firstName], I know you mentioned needing to loop in [other stakeholders]. Here's a summary you can forward: --- **What [productName] does:** [One paragraph summary] **Why it matters for [Their Company]:** - [Specific benefit 1] - [Specific benefit 2] - [Specific benefit 3] **What other [similar companies] have achieved:** [Specific result or case study] **Pricing:** [High-level pricing or "Let's discuss based on your needs"] **Next step:** [Specific action] --- Feel free to forward this as-is, or let me know if you'd prefer I reach out to [other stakeholders] directly. [yourName]
Objection Addresser
Use case: When demo surfaced objections
Description: Following up on concerns raised
Subject line: Thought more about [their concern]
Hi [firstName], I've been thinking about what you said about [their concern/objection]. You raised a fair point. Here's how other customers have handled this: [How similar customers addressed the concern] And here's what we can do specifically for [Their Company]: [Your proposed solution or accommodation] Does this address your concern? Happy to get on a quick call if it's easier to talk through. [yourName]
Timeline Check
Use case: When demo went well but timeline is unclear
Description: Getting clarity on decision process
Subject line: Quick question about timing
Hi [firstName], I really enjoyed our conversation. Before I follow up too much or too little, I wanted to ask: What's your timeline for making a decision on this? I want to be helpful without being annoying. If you're looking to move quickly, I can prioritize getting you whatever you need. If this is more exploratory, I'm happy to check in periodically and give you space. Just let me know where you're at and I'll match your pace. [yourName]
Immediate post-demo follow-up
Thanks for the call + next steps
Hi [firstName],
Thanks for taking the time to chat today. I enjoyed learning about [specific thing they mentioned].
Here's a quick recap of what we discussed:
Your situation: [their problem/challenge] How [productName] helps: [relevant solution points] Next steps: [what you agreed to]
As promised, I'm attaching [whatever you promised: pricing, case study, trial access, etc.].
A few things I forgot to mention:
- [Additional point 1]
- [Additional point 2]
If questions come up as you're reviewing, just reply to this email. I'm also happy to loop in [team member] if you want to go deeper on [technical topic].
Talk soon.
[yourName]
Proposal Follow-Up: Closing the Deal
Once you've sent pricing or a proposal, the follow-up game changes. Now you're dealing with internal processes, budget cycles, and competing priorities.
All Email Sequence Templates
Proposal Check-In
Use case: 3-5 days after sending proposal
Description: First follow-up after proposal
Subject line: Questions on the proposal?
Hi [firstName], Wanted to check in on the proposal I sent over. Have you had a chance to review it? I know these things take time to work through internally. If there are questions, I'm happy to jump on a quick call or address them over email. And if the pricing or terms aren't quite right, let me know. I'd rather find a structure that works than lose the opportunity over something fixable. [yourName]
Internal Champion Support
Use case: When they need to convince others
Description: Helping them sell internally
Subject line: Anything I can do to help make the case?
Hi [firstName], I know getting buy-in for new tools isn't always straightforward. Is there anything I can provide to help you make the case? Some things that have helped other customers: - ROI calculation specific to your situation - Reference call with a similar company - Security/compliance documentation - Executive summary for leadership Just let me know what would be useful and I'll put it together. [yourName]
Urgency Creator
Use case: When deal is stalling
Description: Adding time pressure without being pushy
Subject line: Quick heads up on timing
Hi [firstName], I wanted to give you a heads up: [legitimate reason for urgency, such as pricing changes, capacity constraints, or implementation timeline]. I'm not trying to pressure you. If you need more time, we can figure something out. But I didn't want you to be surprised if [consequence of delay]. What's your current thinking on timing? [yourName]
Alternative Proposal
Use case: When original proposal isn't getting traction
Description: Offering different options
Subject line: Alternative option if [original proposal] is too much
Hi [firstName], I've been thinking about our conversation. If the [original proposal] feels like too big of a commitment, I have an alternative. **Option B:** [Smaller commitment, lower price, or phased approach] This would let you [benefit] without [the barrier they're facing]. If it goes well, we can always expand later. Would this be easier to get approved? Let me know and I can send over updated terms. [yourName]
First follow-up after proposal
Questions on the proposal?
Hi [firstName],
Wanted to check in on the proposal I sent over. Have you had a chance to review it?
I know these things take time to work through internally. If there are questions, I'm happy to jump on a quick call or address them over email.
And if the pricing or terms aren't quite right, let me know. I'd rather find a structure that works than lose the opportunity over something fixable.
[yourName]
Win-Back: Re-engaging Lost Deals
Not every deal closes. But "not now" doesn't mean "not ever." Here's how to re-engage prospects who went dark or chose a competitor. Our win-back email sequence guide covers the longer-term re-engagement strategy for lost deals.
All Email Sequence Templates
The Check-In
Use case: 3-6 months after lost deal
Description: Simple re-engagement after time passes
Subject line: Checking in from [productName]
Hi [firstName], It's been a few months since we talked about [productName]. I wanted to check in and see how things are going. How did the [alternative they chose / decision they made] work out? We've made some improvements since we last talked: - [Improvement 1] - [Improvement 2] - [Improvement 3] If the original timing wasn't right but [problem] is still on your radar, I'd love to reconnect. Either way, I hope things are going well at [Their Company]. [yourName]
The New Feature
Use case: When you've built something relevant to their needs
Description: Re-engaging with product news
Subject line: We built [feature] - thought of you
Hi [firstName], When we talked a few months ago, you mentioned [specific need or objection]. I thought of you because we just launched [feature] that addresses exactly that. Here's how it works: [brief explanation] I know you went with [competitor / different direction], but if that's not working out, or if this changes things, I'd love to reconnect. No pressure. Just wanted you to know we listened to that feedback. [yourName]
The Competitor Pain
Use case: When you know competitor has issues
Description: Re-engaging when competitor may be failing them
Subject line: Are you still happy with [competitor]?
Hi [firstName], I know you went with [competitor] when we talked last. I'm not here to say bad things about them, but I've been hearing from some of their customers that [common complaint]. If that's been your experience, I'd love to show you how [productName] handles it differently. We've specifically built [feature/approach] to avoid that issue. If everything's working great, no worries at all. But I wanted to put the offer out there. [yourName]
The Value Share
Use case: Staying top of mind
Description: Re-engaging with useful content
Subject line: Something useful (no sales pitch)
Hi [firstName], No sales pitch, I promise. Just thought you'd find this useful. I wrote about [relevant topic] based on what I've learned from [number] customers: [link] Given what you're doing at [Their Company], the section on [specific part] might be relevant. If you ever want to revisit [productName], I'm around. But for now, just wanted to share something helpful. [yourName]
Simple re-engagement after time passes
Checking in from [productName]
Hi [firstName],
It's been a few months since we talked about [productName]. I wanted to check in and see how things are going.
How did the [alternative they chose / decision they made] work out?
We've made some improvements since we last talked:
- [Improvement 1]
- [Improvement 2]
- [Improvement 3]
If the original timing wasn't right but [problem] is still on your radar, I'd love to reconnect.
Either way, I hope things are going well at [Their Company].
[yourName]
Founder Sales Best Practices
Personalization That Matters
Don't just insert first names. Personalize on:
- Their specific situation: What are they building, launching, or struggling with?
- Shared experiences: Have you faced the same challenges?
- Mutual connections: Who do you both know?
- Recent news: What have they announced or achieved?
When to Scale (and When Not To)
| Stage | Volume | Personalization |
|---|---|---|
| Pre-PMF | 20-50 emails/week | 100% personalized |
| Early PMF | 50-100 emails/week | 80% personalized |
| Clear PMF | 100-200 emails/week | 50% personalized |
| Growth | Consider hiring | Templatized + personalized |
Don't scale until you know what works. Sending 1,000 bad emails is worse than sending 50 good ones.
Tools for Founder Sales
Keep it simple:
- CRM: Notion, Airtable, or a simple spreadsheet. You don't need Salesforce yet.
- Email: Your regular email works fine. Maybe add a simple scheduling tool.
- Automation: Use Sequenzy to send triggered emails based on user behavior, so you can focus manual effort on cold outreach.
Common Founder Sales Mistakes
- Sounding like a sales rep: Your advantage is authenticity. Don't lose it with corporate speak.
- Giving up too early: Most responses come after email 3-5. Don't stop at one.
- Not following up after demos: The demo is the beginning, not the end.
- Hiding behind email: Sometimes you need to pick up the phone.
- Not asking for the sale: Being too passive. If the fit is there, ask for the commitment.
The Bottom Line
Founder-led sales isn't about being a salesperson. It's about being a founder who sells.
Your emails should sound like they came from the person who built the product, because they did. Your follow-ups should feel like genuine interest, not quota pressure. Your proposals should reflect a desire to solve problems, not just close deals.
The templates in this guide are starting points. Adapt them to your voice, your product, and your prospects. The best founder sales emails don't feel like templates at all. They feel like one human reaching out to another about a problem worth solving.
For more on cold email specifically, check out our guide on cold email sequences. And if you want to automate the behavioral emails (onboarding, activation, conversion) so you can focus on direct outreach, Sequenzy can handle that piece while you focus on the conversations only a founder can have.
For more on the broader sequence strategy behind SaaS sales and marketing, our best email marketing sequence guide covers which sequences drive the most revenue at each stage.
Now go send some emails. Your first customer is waiting.
Frequently Asked Questions
How many cold outreach emails should a founder send per week?
It depends on your stage. Pre-product-market fit, aim for 20 to 50 highly personalized emails per week. Quality beats volume when you are still learning your positioning. As you find repeatable messaging, you can scale to 100 to 200 per week with more templatized approaches. See our cold email sequence guide for volume-specific advice.
What is the best time to send founder sales emails?
Tuesday through Thursday mornings between 8 and 10 AM in the prospect's time zone tend to perform best. Avoid Monday mornings and Friday afternoons. However, as a founder, you can break these rules. Sending at unconventional times (like Sunday evening) can actually stand out because it signals genuine personal effort rather than automated scheduling.
Should I mention that I am the founder in every email?
Yes, in the first email and the signature. It is your biggest differentiator. After the initial outreach, you can drop the explicit mention since they already know. The founder title creates curiosity and increases open rates because people are more likely to engage with someone who built the product.
How do I balance founder sales with building the product?
Block specific time for each. Many founders dedicate mornings to sales outreach and afternoons to product work, or alternate entire days. Batch your email writing: draft all outreach for the week in one sitting, then schedule sends. Automate behavioral emails like onboarding and trial conversion so you can focus manual effort on direct sales conversations.
When should I stop doing founder sales and hire someone?
When you have a repeatable sales process: a consistent message that gets responses, a clear demo flow that converts, and a pipeline that you cannot manage alone. Most founders should keep doing sales through at least the first 50 to 100 customers. Hiring a salesperson before you understand your own sales motion wastes money and time.
How do I handle objections in email?
Address them directly and honestly. If a prospect says your product is too expensive, acknowledge it and explain the value. If they prefer a competitor, ask what specifically they like better. Founders can be more candid than sales reps: "You are right, we do not have that feature yet. Here is what we are building and when it ships." Honesty builds trust faster than deflection.
What should I do with prospects who ghost after a demo?
Send a same-day recap, a value-add follow-up three to four days later, and a break-up email at day 14. If they ghost the break-up email too, add them to a quarterly check-in list. Often the timing was wrong, not the fit. A re-engagement email sequence can automate the long-term nurture.
How do founder sales emails differ from cold email sequences?
Founder sales emails emphasize personal story, product journey, and authentic relationship building. Cold email sequences focus more on value propositions, social proof, and efficient qualification. The founder advantage is that you can speak with unique authority about the problem because you lived it and built the solution.