Back to engineering journal
Lessons Learned•6 min read

125 Days, One Ghost, Zero Dollars: A Love Letter to Every Middleman on Earth

A real story about getting strung along by a client middleman for months — and the one policy change that fixed it for good.

2026-08-30By INQ & Team
KEY TAKEAWAYS

The 125-Day Post-Mortem (TL;DR)

    ★ INQ FOX NOTEINQ Agency Policy

    Transparent scope, upfront milestone commitments, and zero middleman telephone games guarantee both parties are aligned.

    INQ Fox mascot pointing at features

    Every freelance developer horror story begins with someone saying, "Don't worry, the budget is totally locked in."


    Let me tell you about the time I built a high-converting landing page for a client I never talked to, negotiated through a middleman who apparently moonlights as a professional apologizer, and got paid in absolutely nothing for the better part of four months.

    This is the unfiltered autopsy of a freelance client payment disaster, a masterclass in client ghosting, and the exact operational reason we threw our old contracts in the paper shredder and instituted a mandatory upfront payment policy.

    [The Middleman Time Loop]
    Deliver Work ──> "I'll send it today" ──> Next Tuesday ──> "Revisions first" ──> $0 Balance
    

    1. The Setup: Meet "The Vibe Coordinator"

    The deal arrived through a mutual acquaintance. Let’s call him The Vibe Coordinator, because his entire professional job description was "vibes, zero accountability."

    The original scope was straightforward: design and engineer a custom landing page. The quote was completely fair.

    He talked it down. Twice.

    He did this in the sacred name of "good faith," which I have now learned through expensive empirical research is corporate speak for:

    "I plan to consume 120 hours of your life at a 40% discount while taking zero personal financial liability."

    Like an eager developer who still believed the world ran on honor and handshake agreements, I agreed. I fired up the IDE, set up the repo, and got to work.


    2. The Revisions Spiral: Scope Creep as a Fine Art

    The initial build was delivered in under five business days. Sub-second load speed, custom typography, responsive breakpoints, clean code.

    Then came the revisions.

    • "Can we tweak the hero section headline?" — Sure.
    • "Can we try a different CTA color?" — Done.
    • "The photography feels too corporate, can we swap all 14 assets?" — Fine.
    • "Actually, let's redesign the logo, rebuild the navigation drawer, and re-architect the pricing grid." — Alright.

    At some point around week four, I wasn't building a landing page anymore. I was single-handedly curating a living museum exhibit titled:

    Scope Creep: A Retrospective in Unpaid Labor.

    And every time I pushed an updated commit, I asked the same basic question: "Hey, can we settle the milestone invoice before we move to the next phase?"


    3. The "I'll Send It Today" Time Paradox

    Through all of it, one single answer came back on loop, vibrating like a 1998 fax machine having an existential crisis:

    "I'll send it today."

    Not today-today. Never today-today.

    "Today" in the lexicon of dealing with difficult clients and shady agency brokers is an emotional concept, not a recognized unit of solar time.

    • I got "I'll send it today" on a Tuesday.
    • I got "Banking server was down, sending today" the following Tuesday.
    • I got "Accountant is releasing the wire today" three Tuesdays later.

    I am fairly confident that if I go back through my Slack logs, I received a confirmation that the payment was arriving on a Tuesday that hasn't even happened in our Gregorian calendar yet.

    Expected: Invoice Net-14
    Actual:   125 Days ──> 42 Excuses ──> 0 Dollars
    
    INQ Fox developer facepalming while middleman gives excuses like Next Tuesday and accountant on vacation
    Figure 1: The middleman telephone loop — 42 excuses later, the invoice balance is still $0.00.

    4. The Middleman Meltdown: "Contacting the Client Will Make Problems"

    After 90 days of playing telephone with a ghost, I decided to do what any reasonable engineer would do: find the actual company director on LinkedIn, pull their email, and send a polite, professional note asking for payment clearance.

    The Vibe Coordinator intercepted the maneuver and went nuclear.

    He told me — and I want you to genuinely sit with the psychological audacity of this sentence:

    "Contacting the client directly will make problems."

    Not "it isn't necessary." Not "let me handle it."

    Make problems.

    As if the human whose bank account held my overdue invoice was an unexploded WWII ordnance, and The Vibe Coordinator was the only bomb disposal technician certified to defuse it. Except the bomb kept ticking, the bomb kept claiming it had already paid everyone, and somehow my bank balance remained stubbornly at zero dollars.

    So I did the only sane, dignified thing left in the playbook:

    I pulled the DNS records and took the website down.

    Not entirely out of spite — okay, maybe 30% spite — but mostly because hosting and maintaining a digital system that nobody is paying for is called a very expensive hobby, and I already have hobbies that don't involve writing invoices into the void.


    5. The Autopsy: The Single Biggest Threat to Any Project

    Here is the actual business lesson, because I refuse to write 800 words of justified developer rage without giving founders and freelancers something tangible to protect their balance sheets:

    The second there is a middleman between you and the money, the middleman is the project risk.

    It isn't the technical architecture. It isn't the database schema. It isn't even the client's indecisiveness.

    The exact moment someone's full-time job becomes "explaining why the money hasn't arrived," that person is now the single greatest existential threat to your agency's cash flow. You should treat that buffer with precisely the amount of trust it has earned: zero.


    6. The Policy Change: Why We Require Upfront Payment

    At INQ Studios, we don't start builds without upfront milestone commitments anymore.

    INQ Fox developer happily holding 100% Upfront Contract with green checkmark shield and piggy bank
    Figure 2: The Studio Policy Shift — 100% clear milestone commitments before writing a single line of code.
    [The INQ Standard]
    100% Fixed Scope ──> Upfront Milestone ──> 2-4 Week Delivery ──> 100% IP Transfer
    

    Not because we've stopped trusting founders. If anything, my receipts prove I have historically trusted people far too much.

    We do it because:

    1. Trust is not a line item in QuickBooks.
    2. "Today" is not an accepted payment gateway on Stripe.
    3. True partners value skin in the game. When both sides are financially aligned from Day 1, projects ship in 2 to 3 weeks instead of dragging across four miserable months.

    If you are a founder looking to build custom software, SaaS platforms, or high-performance websites, work with engineering teams who value transparent contracts, fixed timelines, and zero middlemen games.


    TIRED OF RUNAROUNDS?

    Ready for Fixed-Price, No-BS Digital Craftsmanship?

    We engineer bespoke websites, SaaS web apps, and automated workflows with guaranteed delivery dates and 100% IP ownership.

    TAGS:Freelance Horror StoryClient ManagementUpfront PaymentsAgency LessonsFounders
    PRODUCTION ENGINEERING SPRINTS

    Need a sub-second, custom Next.js system built for your company?

    We turn ambitious software ideas into high-velocity web applications, SaaS platforms, and internal tools in 3 weeks with 100% intellectual property ownership.

    Chat on WhatsApp