How Technology Solopreneurs Can Use Claude to Fix the Feast-or-Famine Revenue Cycle When Managing Three Client Projects Simultaneously

You are an expert solopreneur business systems consultant with 15 years of experience helping independent technology consultants, developers, and product specialists build pipeline systems that eliminate the feast-or-famine revenue cycle without requiring a sales team or a marketing budget. Help me build a vendor evaluation scorecard so I can reduce information overload and create a system for evaluating new client opportunities that stops me from chasing every lead and missing the ones worth taking. My situation: - Specialty and typical client profile: [e.g., "fractional CTO and technical advisor — clients are Series A and B startups needing architecture decisions and engineering team leadership"] - Current revenue pattern: [e.g., "3-month intensive engagements, 6–8 week gap between projects, revenue swings between $0 and $28,000 per month"] - How I currently find new clients: [e.g., "LinkedIn referrals and former colleague introductions — no outbound, no content, no systematic follow-up"] - Time available for business development when fully engaged: [e.g., "3 hours per week maximum — fully consumed by client delivery when three projects are running simultaneously"] - Biggest decision problem: [e.g., "I say yes to projects that sound interesting but pay poorly and no to projects that pay well but seem less exciting — my evaluation is emotional, not systematic"] - Pipeline visibility right now: [e.g., "a mental list and a notes app — no CRM, no pipeline stage tracking, no follow-up reminders"] - Revenue target and capacity: [e.g., "target $20,000/month consistent — maximum capacity 2 concurrent engagements to protect quality"] Deliver: 1. A vendor evaluation scorecard repurposed as a client opportunity scorecard — ten criteria scored 1–5 across four dimensions (revenue quality, strategic fit, delivery risk, relationship value) with a minimum threshold score below which an opportunity is declined regardless of how interesting it sounds 2. A three-stage pipeline structure for a solopreneur — stages are signal (early interest), qualify (criteria scored), and close (terms under discussion) — with the maximum number of opportunities allowed at each stage before the pipeline is considered full and no new leads are pursued 3. A 3-hour-per-week business development schedule — a fixed weekly block with four sub-tasks (pipeline review, one outreach message, one follow-up, one content touchpoint) allocated by time, designed to fit inside a fully-booked delivery week without requiring a half-day commitment 4. A minimum viable CRM setup using Notion — a database with eight fields, three views (pipeline kanban, follow-up due, won and lost analysis), and a weekly update protocol that takes 20 minutes to maintain 5. A client qualification conversation guide — eight questions asked in the first 30-minute discovery call that populate the scorecard criteria, identify red flags that are not visible on a brief, and surface the client's true decision timeline 6. A retainer proposal framework for converting project-based clients into recurring engagements — a one-page structure that presents three options (project only, project plus monthly retainer, retainer only) and the value argument for each, targeted at clients who are likely to need ongoing advisory support after the initial engagement closes 7. A referral activation sequence — a three-message outreach cadence sent to the five highest-value former clients, structured to generate a warm referral or a direct re-engagement within 30 days without feeling transactional 8. A quarterly revenue forecast template — uses current pipeline stage and close probability to project the next three months of revenue, flags the month most at risk of a gap, and triggers a specific prospecting action when forecast revenue drops below the monthly target **Write every output assuming the solopreneur is excellent at delivery and terrible at selling — every framework must feel like a decision system, not a sales process, because the only way this person will use it consistently is if it feels like it protects their time rather than demands more of it.**