Timmy_Foundation/the-nexus
15
1
Fork 2
Code Issues 79 Pull Requests 70 Actions Packages Projects Releases Wiki Activity
Files
748c7b87c52f3276080a23dff610ad91f5ff2b3c
the-nexus/reviews/2026-04-06-operation-get-a-job-review.md
Allegro d3056cdac5
Some checks failed
Deploy Nexus / deploy (push) Has been cancelled
Details
review: 2026 04 06 operation get a job review
2026-04-06 22:31:46 +00:00

28 KiB
Raw Blame History

Operation Get A Job — Honest Review

Reviewed: April 2026 Reviewer: Critical subagent (no sugar-coating)

OVERALL ASSESSMENT

The package is well-structured and professional-looking. The problem is that it reads like it was written by someone who already has 10 clients, not someone who has zero. Multiple files contain inflated claims, unrealistic pricing for a brand-new firm with no track record, and confidence language that would ring hollow to any experienced CTO who does 30 seconds of research and finds... nothing. No LinkedIn history, no public portfolio, no testimonials, no case studies, no Google results.

The bones are good. The tone needs to come down to earth.

FILE-BY-FILE FINDINGS

1. README.md (Master Plan)

ISSUES:

  1. "We are not a solo freelancer. We are a firm with a human principal and a fleet of five autonomous AI engineers that ship production code 24/7."

    • PROBLEM: This is a solo freelancer with AI tools. Every client will see through this framing instantly. Calling AI agents "engineers" invites skepticism and mockery. A CTO will ask "so it's just you with ChatGPT?" and Alexander needs to have a better answer than "no, it's FIVE ChatGPTs."
    • FIX: "We are a solo engineering practice that uses a fleet of AI agents to multiply output. Alexander handles architecture, client relationships, and quality review. The agents handle implementation, testing, and automation under his direction."

  2. "$5k-15k first month" revenue target (Phase 3)

    • PROBLEM: This is optimistic for a brand-new firm with no portfolio, no testimonials, and no network. More realistic first month: $0-5k. It takes 4-8 weeks just to get through the pipeline from first outreach to first payment.
    • FIX: Change to "$0-5k first month (realistic), $5-15k by month 2-3 if pipeline is worked consistently."

  3. "$20-40k/month" by Month 2-3 (Phase 4)

    • PROBLEM: This is fantasy for a solo practitioner 60-90 days in. Even established consultancies with reputations take 6-12 months to hit this. This kind of projection will make Alexander complacent or demoralized when reality doesn't match.
    • FIX: Change to "$10-20k/month by month 4-6 (aspirational)." Remove "hire subcontractors for overflow" — there won't be overflow in month 2.

  4. Revenue metrics table: Month 1 = $10-15k, Month 3 = $30-50k

    • PROBLEM: Same issue. These are hype numbers.
    • FIX: Month 1 = $0-5k, Month 3 = $10-20k.

  5. "Any project under $2k: decline"

    • PROBLEM: When you have zero clients and zero revenue, you don't decline $2k projects. You take them, deliver excellence, get a testimonial, and upsell.
    • FIX: Change to "Any project under $500: decline. Projects $500-2k: take selectively as portfolio builders if they can become case studies."

  6. "Any project requiring on-site: decline unless >$500/hr"

    • PROBLEM: With no track record, no one is paying $500/hr for on-site. This rule just means "decline all on-site work," which is fine, but say that instead.
    • FIX: "Any project requiring on-site: decline for now (revisit when rates support it)."

  7. Phase 1 ordering: EIN is listed as step 3 but Mercury is step 2

    • PROBLEM: You need the EIN before you can open Mercury. The checklist has them in the right dependency order in entity-setup.md but the README lists Mercury before EIN.
    • FIX: Reorder to: Form LLC → Get EIN → Open Mercury.

  8. "Toptal/Gun.io — Apply to premium freelance networks"

    • PROBLEM: Toptal has a rigorous screening process that takes weeks and includes live coding interviews. Gun.io is similar. These aren't "apply and start bidding" platforms. Alexander should know what he's getting into.
    • FIX: Add note: "(Note: these have multi-week screening processes with technical interviews. Apply early but don't count on them for Week 2-4 revenue.)"

2. entity-setup.md

ISSUES:

  1. Step ordering is correct — this file is actually well-structured. LLC → Agent → File → EIN → Operating Agreement → Bank → Invoicing → Insurance → Tax → Presence. Good.

  2. "Elect S-Corp taxation (Form 2553) if revenue exceeds ~$40k/year"

    • PROBLEM: This is not wrong, but it's missing critical context. S-Corp election has a deadline (due within 75 days of formation, or by March 15 for the tax year). You also need to pay yourself a "reasonable salary" which adds payroll complexity and cost ($40/mo for Gusto + payroll tax filings). For a new firm with uncertain revenue, this is premature.
    • FIX: Add: "DO NOT elect S-Corp until you've had at least 2-3 months of consistent revenue above $5k/month. Consult a CPA before filing Form 2553. The S-Corp election deadline is 75 days from formation or March 15 of the tax year. You can always elect later."
    • DISCLAIMER NEEDED: "This is not tax advice. Consult a CPA for your specific situation."

  3. "Get a CPA familiar with LLCs ($200-500/year for filing)"

    • PROBLEM: $200-500/year for a CPA who does LLC tax filing is at the very low end. More realistic: $500-1,500 for a basic LLC return, more if S-Corp.
    • FIX: Change to "$500-1,500/year for LLC filing, $1,000-2,500 if S-Corp."

  4. Bench.co pricing: "$300-500/mo"

    • PROBLEM: Bench's current pricing starts higher and has changed frequently. This may be outdated.
    • FIX: Add "(verify current pricing)" after all third-party service prices.

  5. E&O Insurance at $150/month

    • PROBLEM: This is roughly right for tech consulting E&O, but it's a lot of cash burn for a firm with $0 revenue. Alexander should consider whether he actually needs this before his first client.
    • FIX: Add note: "You can delay E&O insurance until you have a signed client. Some clients will require it. Get quotes early but don't bind the policy until you need it."

  6. Total startup costs: ~$330

    • PROBLEM: This doesn't include the operating agreement ($0-500), a domain ($12), or the first month of email ($6). Minor, but the total should be honest.
    • FIX: Change to "~$330-500 depending on whether you use a free or paid operating agreement template."

  7. "You can go from zero to invoicing in under a week."

    • PROBLEM: This is aspirational. Mercury alone can take 3-7 business days for approval, and sometimes longer if they request additional documentation. EIN online portal has limited hours.
    • FIX: "You can go from zero to invoicing in 1-2 weeks. Don't let entity setup be a blocker — start conversations while the paperwork is processing."

3. service-offerings.md

ISSUES:

  1. "We deliver at the speed and consistency of a 10-person team with the overhead of one."

    • PROBLEM: This is a claim that cannot be substantiated and will make any experienced technical buyer roll their eyes. Five AI agents do NOT equal 10 engineers. They can do certain tasks well (boilerplate code, test writing, documentation) but they can't do architecture, complex debugging, or novel problem-solving the way 10 humans can.
    • FIX: "We deliver faster than a traditional solo practice by leveraging AI agents for implementation, testing, and automation — while keeping overhead low."

  2. Tier 1 pricing: $400-600/hr

    • PROBLEM: This is Big 4 consulting / top-tier FAANG contractor pricing. Deloitte charges $400-600/hr for a senior partner. A brand-new LLC with no case studies, no testimonials, no public track record charging $600/hr is laughable. Even $400/hr is a stretch. The client will Google "Whitestone Engineering" and find nothing.
    • FIX: Launch pricing should be $150-250/hr for Tier 1. You can raise rates after you have 3-5 happy clients and case studies. Put a note: "Introductory rates — will increase as client base grows."

  3. Tier 2 pricing: $250-400/hr

    • PROBLEM: Same issue, slightly less extreme. AI security auditing is specialized, but $400/hr requires established reputation.
    • FIX: $125-200/hr at launch.

  4. Tier 3 pricing: $150-250/hr

    • PROBLEM: The low end ($150) is actually reasonable for automation/DevOps work. The high end ($250) is a stretch for a new firm doing commodity CI/CD work.
    • FIX: $100-175/hr at launch.

  5. Advisory/Consulting: $300-500/hr (from rate-card.md)

    • PROBLEM: Nobody pays $500/hr for advice from someone they've never heard of. Advisory rates are earned through reputation.
    • FIX: $150-250/hr at launch.

  6. "CVE-class vulnerability identification and remediation"

    • PROBLEM: This implies Alexander and the fleet can find zero-day vulnerabilities. Can they? If not, this is misleading. "CVE-class" means "severity level worthy of a CVE," which is a very specific claim.
    • FIX: Change to "Vulnerability identification and remediation" without the CVE-class qualifier unless Alexander has actual CVE credits.

  7. "Conscience validation systems (ethical guardrails that actually work)"

    • PROBLEM: "(ethical guardrails that actually work)" is a dig at competitors. It's unprofessional and unsubstantiated in a service listing. Save the attitude for blog posts.
    • FIX: "Conscience validation systems — runtime ethical guardrails for AI agent behavior"

  8. Package pricing: Starter $5k, Professional $15k, Enterprise $40k+

    • PROBLEM: The Starter at $5k is reasonable. The Professional at $15k is aggressive but defensible if the deliverables are real. The Enterprise at $40k+ is aspirational — no new firm is closing $40k deals in month 1. This is fine to have on the menu, but don't expect it to move early.
    • FIX: Add a "Launch Special" or "Pilot" package at $2,500-3,000 that gets a client a single basic agent deployment with minimal customization. This is the foot-in-the-door offer.

  9. Comparison table: "Cost: Traditional $300-500/hr billed | Competitive, transparent"

    • PROBLEM: You're charging $400-600/hr yourself (Tier 1). How is that "competitive" vs. traditional at $300-500? This is contradictory.
    • FIX: Either lower your rates or remove the cost comparison row.

  10. "battle-tested Hermes framework"

    • PROBLEM: Battle-tested by whom? By Alexander's own agents on his own projects. No external clients have used it. "Battle-tested" implies production use by multiple organizations.
    • FIX: "our Hermes framework" — drop "battle-tested" until you have client deployments.

4. portfolio.md

ISSUES:

  1. "This is not a demo. This is not a prototype. Everything below is running in production."

    • PROBLEM: It IS running in production — Alexander's production. But a client reading this would expect "production" to mean "deployed for paying customers." Be clear.
    • FIX: "Everything below is running in our production environment — the same infrastructure we use daily to operate our engineering practice."

  2. "43 active repositories" / "16 organization members"

    • PROBLEM: If a client asks for access to the Gitea forge to verify, can Alexander show it? Are these repos meaningful, or are some empty/trivial? 16 "organization members" — are 5 of these the AI agents, meaning there are 11 humans? Who are the other 10? If it's actually 1 human + 5 AI accounts + 10 bot/service accounts, saying "16 organization members" is misleading.
    • FIX: Be honest about what the number means. "43 repositories (core framework, agent configurations, tools, and project code)" and clarify the member count or just remove it.

  3. "3,000+ automated tests"

    • PROBLEM: This is repeated across every file like a mantra. If a client asks to see the test suite, can Alexander show it? Are these meaningful tests or padded parameterized tests? This number needs to be real and verifiable.
    • FIX: Keep the claim only if it's genuinely accurate. If some are trivial/generated, say "comprehensive test suite" instead of citing a number.

  4. GOFAI Hybrid Neuro-Symbolic Reasoning section

    • PROBLEM: This sounds impressive but vague. What does it actually do? What problems has it solved? If a CTO asks "show me the symbolic reasoning engine," can Alexander demo it? If it's experimental/early-stage, it shouldn't be in the portfolio as a "Production System."
    • FIX: Either add concrete details about what it does and what results it produces, or move it to an "R&D / Experimental" section.

  5. Evennia MUD section

    • PROBLEM: A MUD (Multi-User Dungeon) in a professional engineering portfolio is going to confuse enterprise clients. "Used internally for agent training and scenario modeling" — is this real or aspirational? If it's real, explain the business value. If not, remove it.
    • FIX: Either explain clearly how this provides business value ("Virtual environment for testing agent behavior under controlled conditions — used to validate agent responses before production deployment") or remove from the main portfolio and list under "Internal Tools."

  6. "We've Already Solved the Hard Problems" section

    • PROBLEM: Arrogant tone. A client who has spent years building AI systems won't appreciate being told someone solved all the hard problems. Especially by a firm with no public track record.
    • FIX: "We've Tackled These Challenges In Our Own Systems" — more humble, still credible.

  7. No case studies

    • PROBLEM: The case study section is empty (template only). This is honest, but it highlights that there are ZERO client references. This is the single biggest weakness.
    • FIX: Do 1-2 projects at cost or free to build case studies. Even internal "case studies" framed as "how we built X for our own operations" would be better than nothing. Write 2-3 internal case studies in the format provided.

5. outreach-templates.md

ISSUES:

  1. Template 1 (Upwork): "This is exactly what my firm does day in, day out."

    • PROBLEM: Sounds salesy. On Upwork, proposals that start with "this is exactly what we do" are a dime a dozen. Every bidder says this.
    • FIX: Cut the first sentence. Start with the specific — immediately reference something from their job post and show you read it.

  2. Template 1 repeats the full pitch every time: "fleet of five autonomous AI agents... 43-repo forge... 15-minute autonomous work cycles 24/7"

    • PROBLEM: This is too much for an Upwork proposal. The client doesn't care about your internal infrastructure. They care about whether you can solve their problem.
    • FIX: Cut the self-description to one sentence: "We're a small engineering firm that builds and operates production AI agent infrastructure." Then go straight to how you'd solve their specific problem.

  3. Template 2 (LinkedIn): "No pitch — just want to see if there's a fit."

    • PROBLEM: This IS a pitch. Saying "no pitch" while pitching is a well-known sales tactic that makes people trust you less, not more.
    • FIX: Remove "No pitch —". Just ask the question directly: "Would 15 minutes be worth it to discuss [SPECIFIC PAIN POINT]?"

  4. Template 3 (Twitter): "we solved this exact problem"

    • PROBLEM: Presumptuous. You solved YOUR version of this problem. You don't know their specific constraints.
    • FIX: "We ran into something similar and built [X]. Here's what worked for us:"

  5. Template 3C: "Might save your team months."

    • PROBLEM: Unsubstantiated claim. How do you know? You haven't talked to them yet.
    • FIX: Remove this sentence entirely.

  6. Template 4 (Discord Community Post):

    • PROBLEM: This is actually the best template in the file. Value-first, technical, specific. The "systemd > Docker" hot take is good engagement bait. Keep this mostly as-is.
    • MINOR FIX: "[X]% of agent operations" — fill in an actual percentage or remove the claim.

  7. Template 5 (Cold Email): Too long

    • PROBLEM: The cold email is 15+ lines with a bullet list of everything ever built. Cold emails should be 5-7 lines max. Decision-makers don't read long emails from strangers.
    • FIX: Cut to: 2-line intro → 2-line "why I'm emailing you" → 1-line credibility → 1-line CTA. Move the full capability list to the portfolio link.

  8. General issue across all templates: Over-reliance on the same stats

    • PROBLEM: Every template mentions "5 agents, 43 repos, 3,000 tests, 15-minute burn cycles." By the time a prospect sees this for the third time, it feels like a script. Also, these are vanity metrics — clients care about outcomes, not your internal metrics.
    • FIX: Lead with outcomes and client-relevant capabilities. Save the internal metrics for the portfolio page.

  9. Conversion math at the bottom: "~100 outreach messages to land ~1 client"

    • PROBLEM: This is actually realistic for cold outreach. Good to set expectations. Keep this.

6. proposal-template.md

ISSUES:

  1. Structure is solid. Executive summary → problem understanding → solution → timeline → pricing → terms → acceptance. This is professional and well-organized.

  2. "About Whitestone Engineering" section repeats the same stats AGAIN

    • PROBLEM: If the client got an outreach message, saw the portfolio, and is now reading the proposal, they've seen "5 agents, 43 repos, 3,000 tests" three times already.
    • FIX: Keep it brief in the proposal. 2-3 sentences max. Link to portfolio for details.

  3. Acceptance section with signature lines

    • PROBLEM: A proposal with signature lines that doubles as a contract is legally ambiguous. The proposal says "By signing below, [CLIENT] accepts this proposal and authorizes [FIRM] to proceed... under the terms outlined above." But the terms are thin — no IP assignment clause, no limitation of liability, no indemnification, no confidentiality, no dispute resolution, no governing law.
    • FIX: Either (a) remove the signature section and have a separate MSA/SOW that gets signed, or (b) add proper legal terms. Option (a) is safer and more professional. The proposal should say "This proposal is not a contract. A Master Services Agreement will be provided for signature upon acceptance."
    • DISCLAIMER NEEDED: Alexander should have an attorney review any contract before using it with clients. Template contracts from the internet can miss state-specific requirements.

  4. "Client owns all deliverables upon final payment"

    • PROBLEM: This is a significant business decision. Work-for-hire means Alexander can't reuse any client-specific code. This is fine and standard, but make sure Alexander understands the implication — he can't take Client A's custom agent setup and deploy it for Client B.
    • FIX: The current language about retaining "general knowledge and techniques" is good. Consider adding: "Whitestone Engineering retains ownership of pre-existing tools, frameworks, and libraries used in the engagement." This protects Hermes from being claimed by a client.

  5. "Either party may terminate with 14 days written notice"

    • PROBLEM: If the client terminates after paying 50% deposit on day 3, what happens? Is the deposit refundable? What about work completed?
    • FIX: Add: "Upon termination, client pays for work completed to date. Deposits are non-refundable but are credited toward completed work."

7. rate-card.md

ISSUES:

  1. All hourly rates are too high for a new firm (see service-offerings.md analysis above)

    • Emergency/Incident Response at $500-800/hr is especially egregious. Who is calling a firm with no track record for emergency incident response?
    • FIX: See recommended rates below.

  2. Pre-paid hour blocks: 10hrs at $300/hr, 100hrs at $225/hr

    • PROBLEM: The discount structure assumes the base rate is ~$350/hr. If we adjust base rates down, these need to scale down too.
    • FIX: Adjust proportionally with new base rates.

  3. Retainer: Advisory at $3,000/mo for 10 hours = $300/hr effective

    • PROBLEM: Same rate issue. Also, who is buying advisory retainers from a new firm? This tier won't move early.
    • FIX: Keep the structure but adjust rates. Consider a $1,500-2,000/mo tier with 10 hours for early clients.

  4. "1-2 week queue" for non-retainer clients

    • PROBLEM: There is no queue. Alexander has zero clients. Claiming a queue when you have none is dishonest.
    • FIX: Remove the "1-2 week queue" language until it's real. Replace with "Retainer clients get priority scheduling."

  5. Minimum engagement: $3,000

    • PROBLEM: Too high for a new firm. Again, when you have no clients, a $1,500 project that becomes a case study is worth more than holding out for $3,000.
    • FIX: Change to $1,500 minimum, with a note that projects under $3,000 require full prepayment.

  6. "Rates subject to change. This rate card supersedes all previous versions."

    • PROBLEM: There are no previous versions. This is fine boilerplate but slightly silly for v1.
    • FIX: Keep it — it's harmless and future-proofs the document.

RECOMMENDED LAUNCH RATES

These are realistic rates for a new firm with no established client base, competing on Upwork and cold outreach:

Service Category Launch Rate Rate After 5+ Clients
Agent Infrastructure $150 — $250/hr $250 — $400/hr
Security & Hardening $125 — $200/hr $200 — $350/hr
Automation & Research $100 — $175/hr $150 — $250/hr
Advisory / Consulting $150 — $250/hr $250 — $400/hr
Emergency / Incident $250 — $400/hr $400 — $600/hr

Package deals:

Package Launch Price Post-Track-Record Price
Pilot (NEW — add this) $2,500 Remove after month 3
Starter $3,500 — $5,000 $5,000 — $8,000
Professional $10,000 — $12,000 $15,000 — $25,000
Enterprise $25,000+ $40,000+

LEGAL / TAX DISCLAIMERS NEEDED

These should be added:

  1. entity-setup.md — Add at top: "NOTE: This document contains general information, not legal or tax advice. Consult a licensed attorney and CPA for your specific situation."

  2. entity-setup.md, tax section — Add: "S-Corp election has complex timing and salary requirements. Do not file Form 2553 without consulting a CPA."

  3. proposal-template.md — Add note: "Have an attorney review your MSA and SOW templates before sending to clients. Template contracts may not comply with your state's laws."

  4. rate-card.md — Add: "Payment terms and late payment interest rates must comply with applicable state laws."

THINGS THAT WOULD EMBARRASS ALEXANDER

  1. Charging $600/hr with no clients, no case studies, no Google results for "Whitestone Engineering." A CTO will laugh.
  2. Claiming "10-person team output" without evidence.
  3. Saying "battle-tested" for internal-only systems.
  4. The MUD (Evennia) in a professional portfolio without clear business justification.
  5. "No pitch" in a message that is clearly a pitch.
  6. Having signature lines on a proposal with insufficient legal terms.
  7. Claiming a "1-2 week queue" when the queue is empty.
  8. Repeating "5 agents, 43 repos, 3,000 tests" in every single document like a broken record.

ALEXANDER'S CHECKLIST — Exact Steps In Order

WEEK 1: Entity + Foundation

Day Task Time Cost
Mon Decide firm name, check Wyoming SOS availability 30 min $0
Mon Order Wyoming Registered Agent ($60/yr) 15 min $60
Mon File Wyoming LLC Articles of Organization online 30 min $100
Tue-Wed Wait for LLC confirmation (1-2 biz days) — —
Wed Get EIN online (IRS, Mon-Fri 7am-10pm ET only) 15 min $0
Wed Download operating agreement template (Northwest RA free template or LawDepot) 30 min $0
Wed Apply for Mercury business bank account 20 min $0
Thu Register domain (firm name .com) 15 min $12
Thu Set up Google Workspace email (hello@firm.com) 30 min $6/mo
Thu Create LinkedIn personal profile update + company page 1 hr $0
Fri Write 3 internal "case studies" about Hermes, CI/CD, and agent security 3 hrs $0
Fri Deploy simple portfolio site (static, from portfolio.md content — stripped down) 2 hrs $0
Sat Create Upwork account/profile 1 hr $0
Sun Write elevator pitch (60 seconds, practice out loud 10 times) 1 hr $0

Week 1 spend: ~$178 + $6/mo Week 1 goal: LLC filed, EIN obtained, bank account pending, portfolio site live, Upwork profile created.

WEEK 2: Pipeline Building

Day Task Time Cost
Mon Mercury account should be approved — verify and set up 30 min $0
Mon Set up Stripe connected to Mercury 30 min $0
Mon Send 5 Upwork proposals (use simplified Template 1) 2 hrs $0
Tue Send 5 LinkedIn DMs to CTOs at AI startups (Template 2, simplified) 2 hrs $0
Wed Write one technical post for LinkedIn/Twitter about agent operations 1 hr $0
Wed Join 2-3 Discord communities (AI builders, DevOps) 1 hr $0
Thu Post value-first content in Discord (Template 4A) 1 hr $0
Thu Send 5 more Upwork proposals 2 hrs $0
Fri Follow up on any responses, refine pitch based on feedback 2 hrs $0
Fri Apply to Toptal (start the screening process) 1 hr $0
Weekend Get E&O insurance quote (don't bind yet unless client requires) 30 min $0

Week 2 spend: $0 Week 2 goal: 10+ Upwork proposals sent, 5+ LinkedIn DMs sent, 1 community post, Stripe live, first follow-ups sent.

WEEK 3: Close First Deal

Day Task Time Cost
Mon Send 5 more Upwork proposals + follow up on Week 2 outreach 2 hrs $0
Mon Send 5 cold emails (Template 5, shortened version) 2 hrs $0
Tue Take any discovery calls that come in (free 30 min) 1-2 hrs $0
Tue Write + send first proposal if there's a warm lead 2 hrs $0
Wed Continue outreach cadence (5 new touches minimum) 1 hr $0
Wed Write another technical post (build public presence) 1 hr $0
Thu Follow up on proposals sent 1 hr $0
Thu If a client needs E&O cert, bind insurance now 30 min ~$100-150
Fri Pipeline review: how many leads, what's working, what's not 1 hr $0
Fri Adjust rates/messaging based on feedback (if getting no responses, lower rates or change pitch) 1 hr $0

Week 3 spend: $0-150 (insurance only if needed) Week 3 goal: 25+ total outreach messages sent, 1-3 discovery calls taken, 1-2 proposals out, first deal possible but not guaranteed.

CRITICAL MINDSET ADJUSTMENTS

  1. Your first 3 clients are marketing investments, not profit centers. Price to win, deliver to impress, get testimonials and case studies. Then raise rates.

  2. Nobody cares about your internal infrastructure. Clients care about: Can you solve my problem? How fast? How much? Have you done it before? Lead with THEIR problem, not YOUR setup.

  3. "AI-augmented" is your pitch, not "AI workforce." The moment you frame your agents as a "team," clients will expect team-level accountability and communication. Frame them as tools that make you faster.

  4. The portfolio is your weakest link. You have impressive internal systems but zero client work. Fix this by doing 1-2 projects at discounted rates specifically to build case studies.

  5. Drop the ego pricing. $600/hr is what you charge when someone Googles your name and finds 50 testimonials, 3 conference talks, and a published book. Not when they find a blank LinkedIn company page.

SUMMARY OF ALL RECOMMENDED FIXES

Must-Fix (Do Before Sending Anything to a Client)

  • Lower all rates to launch rates (see table above)
  • Add a $2,500 "Pilot" package
  • Remove "battle-tested" language
  • Remove "10-person team" claim
  • Remove "1-2 week queue" claim
  • Fix the comparison table contradiction (competitive pricing while charging $600/hr)
  • Add legal/tax disclaimers
  • Remove or fix the proposal signature section (separate MSA needed)
  • Add pre-existing IP protection clause to proposal terms
  • Shorten cold email template to 5-7 lines
  • Remove "no pitch" from LinkedIn template
  • Clarify "16 organization members" in portfolio
  • Move Evennia MUD to "Internal Tools" or add clear business justification
  • Lower minimum engagement to $1,500

Should-Fix (Before Month 2)

  • Write 2-3 internal case studies
  • Reduce repetition of "5 agents, 43 repos, 3,000 tests" across documents
  • Make GOFAI section more concrete or move to R&D
  • Adjust revenue projections to realistic numbers
  • Have an attorney review MSA template ($300-500)

Nice-to-Fix (When Time Allows)

  • Fill in the [X]% placeholder in Discord template
  • Add a "What Our Clients Say" section (even if empty, shows intent)
  • Create a one-page PDF version of the rate card for email attachments
  • Set up a scheduling link (Calendly free tier)

Report generated April 2026. Be honest, be humble, get the first client. Everything else follows from there.

Reference in New Issue View Git Blame Copy Permalink