Build a Lead Gen Machine with DenchClaw, Part 5: Close

This is the final part of the Build a Lead Gen Machine series. We've built capture, enrichment, qualification, and outreach. Now we close — converting replies into meetings, meetings into proposals, and proposals into revenue.

More importantly, we close the loop: every closed deal gets tracked back to its original lead source, so you know exactly what's working.

The Close Phase in Context#

At this point in your machine:

• Leads are captured and scored
• Qualified leads have been reached out to
• Replies are coming in

The close phase covers everything from first reply to signed contract. It's less about automation and more about using DenchClaw as your command center to stay organized and never drop the ball.

Step 1: Convert Leads to Deals#

When a lead responds positively and agrees to a meeting:

Convert Sarah Chen's lead to a deal. Company: Stripe. Value: $15,000. Stage: Discovery. Close date: end of Q2.

DenchClaw:

• Creates a new entry in the Deals object
• Links it to Sarah Chen in Contacts
• Links to Stripe in Companies
• Sets Stage to Discovery
• Updates Sarah's Lead Status to "Converted"

The lead remains in your Leads object for analytics. The deal lives in Deals where it belongs.

Step 2: Discovery Prep and Execution#

Before your discovery call:

I have a discovery call with Sarah Chen at Stripe in 30 minutes. Brief me from her lead record and the deal room.

DenchClaw pulls:

• Lead score and qualifying signals
• Enrichment data (company size, funding, tech stack)
• Email thread summary
• Any previous context

You go into the call knowing: why she responded, what she's likely evaluating, and what your best angle is.

After the call:

Discovery call with Stripe done. Notes: Sarah's team uses HubSpot. 3 reps, frustrated with HubSpot cost ($450/mo). Evaluating alternatives. Decision by end of month. Next: send demo invite to Sarah + Marcus Liu (CFO). Move to Proposal stage.

DenchClaw updates the deal, logs the notes, moves the stage, and creates a follow-up task.

Step 3: Demo Management#

For demos, preparation is the difference between a 40% and 70% close rate.

Create a demo prep checklist for the Stripe deal:
- Review their current HubSpot configuration (what features do they use?)
- Prepare a demo environment that mirrors their use case (3-rep sales team, deal tracking)
- Prepare cost comparison: HubSpot $450/mo vs DenchClaw $0
- Prepare for CFO objections: security, support, longevity

DenchClaw creates this as a checklist in the deal room. Check items off as you complete them.

Post-demo:

Demo with Stripe team done. Went well — Marcus asked about SOC2 and data residency. Sarah loves the kanban view. Action items: send security overview by tomorrow, pricing proposal by Thursday.

Step 4: Proposal Generation#

Generate a proposal for the Stripe deal:
- Summary of their needs (from discovery and demo notes)
- DenchClaw solution overview
- Pricing: free tier initially, Dench Cloud at $X/month for team hosting
- Implementation timeline: 2 weeks
- ROI: saving $450/mo from HubSpot, plus X hours/week in rep productivity
- Next steps

DenchClaw drafts the proposal as a document. Review it, adjust pricing and specifics, then:

Export the Stripe proposal as a PDF

Or publish it via here-now for a shareable link.

Step 5: Negotiation Tracking#

When negotiations start:

Stripe came back: they want a 20% discount and a 30-day pilot before committing. Update the deal room with their counteroffer. What's our best response strategy?

DenchClaw logs the negotiation note and can help you think through your response:

• What's the cost of offering a 30-day pilot?
• What are the risks of the discount?
• What's their alternative (stay on HubSpot)?

Track every negotiation step in the deal document. When you hand off internally or loop in a finance person, the history is there.

Step 6: Close and Record the Win#

When they sign:

Stripe deal closed won. $12,000 annual. Contract start: April 1.

DenchClaw:

• Moves deal to Closed Won
• Records the close date and final value
• Updates the linked contact and company records
• Triggers the win analytics

Then close the loop to lead source:

What lead source did the Stripe deal come from? What was their original lead score?

Answer: LinkedIn import, lead score 78. This data goes into your source-to-revenue analytics.

Step 7: Source-to-Revenue Analytics#

The most important analytics in your lead gen machine:

Show me revenue by lead source for the last 6 months: total closed won value, number of deals, and average days from lead capture to close — broken down by LinkedIn/Apollo/Inbound/Referral

What's the conversion rate from qualified lead to closed won, by source?

Which lead score range has the highest close rate? What's the ROI of the enrichment investment?

These numbers tell you where to invest. If Referral leads close at 40% and LinkedIn leads close at 8%, do more for referral generation.

Step 8: Celebrate and Learn#

After every closed deal:

Add a win note to the Stripe deal: what worked, what almost killed the deal, what we'd do differently

After every lost deal:

Add a loss analysis to the Acme deal: lost to Salesforce on security requirements. What could we have done differently?

These notes are your most valuable sales asset. Review them quarterly.

The Complete Machine: What You've Built#

Across all five parts, you've built:

1. Lead Capture — Multi-source import, browser-based scraping, form capture, inbound signals
2. Enrichment — AI-powered company data, tech stack, intent signals, email validation
3. Qualification — Scoring model, ICP match, rep prioritization views
4. Outreach — Personalized AI email sequences, LinkedIn touches, reply management
5. Close — Discovery prep, demo management, proposal generation, deal tracking, revenue analytics

All running locally in DenchClaw, on your machine, with your data never leaving your control.

The entire stack is free and open source. No per-seat fees, no API limits, no vendor lock-in.

For the full DenchClaw feature overview, see what is DenchClaw or start from scratch with the zero to CRM guide.

Frequently Asked Questions#

How long does it take to build this entire system?#

Setting up all five phases takes about a weekend. Running it for the first time with a batch of 50 leads takes another 2-3 hours. After that, maintenance is a few hours per week.

Can I use this system for B2C leads?#

Yes, with adjustments. Replace company-level enrichment with social profile enrichment. Adjust scoring for B2C signals. The pipeline stages change but the architecture is the same.

How does the source-to-revenue attribution work technically?#

The Lead Source field on your Leads object gets carried forward when you convert a lead to a deal (you specify it during conversion). DuckDB then joins Leads and Deals on the contact to run attribution queries.

What's a realistic conversion rate from captured lead to closed won?#

For cold outbound B2B: 0.5-2% from raw lead to closed won is typical. For enriched, scored, personalized outreach: aim for 2-5%. Track your numbers and compare.

Can this system run automatically without daily attention?#

Enrichment and scoring can run fully automated. Outreach requires your review (by design). The close phase is inherently manual. Budget 30 minutes/day for reviews and responses.

Ready to try DenchClaw? Install in one command: npx denchclaw. Full setup guide →