Jackeline

Jackeline

Jackie Hermes

About

My first client ever desperately needed a website, messaging and leads. Their agency delivered a jingle. (It's so absurd that it sounds made up. I know. Stick with me.)

Forums

•

1d ago

How to structure a client discovery call so you never write unpaid proposals

Spending four hours writing detailed project proposals for prospects who simply vanish afterward used to drain half my working week. I realized I was giving away my entire strategic roadmap during free intro calls before confirming they had an actual budget.

Now I treat the initial twenty-minute call strictly as a mutual qualification screen rather than a free consulting session. I ask three targeted questions about their current workflow bottleneck, their desired launch timeline, and the approximate budget allocated for fixing it.

If the numbers align, I summarize the agreed scope in a simple one-page agreement before drafting any detailed architecture. My close rate doubled while my unpaid prep work dropped to almost zero.

  • Confirm budget ranges and decision timelines during the first ten minutes of the conversation.

  • Replace multi-page custom proposals with a concise one-page scope summary for qualified leads.

Google's new agent works on your product until a metric moves. Which one would you hand over?

An agent that chases a number will usually get you that number. I'd like to hear which of your numbers you'd be comfortable handing over, and which you wouldn't.

On 18 November Google Labs announced Stitch Loop, which it describes as a long-running product agent. I'm going by Google's own blog post, written by Justin Toupin, a director of product management at Google Labs. It's an experiment with a waitlist and I haven't used it. The post gives no pricing, no customer results and no stated limitations, so everything below is what Google says it does, not what anyone has seen it do.

The idea is that you connect your GitHub repo and your product context, meaning logs, user behaviour and feedback, through what Google says are over 180 integrations. Then you set up loops. Three come by default: security, latency and accessibility. You can add your own, and Google's example is improving checkout conversion.

Each loop has four steps. It suggests opportunities based on evidence from your product. It proposes one or more solutions with the tradeoffs. It builds the one you pick in a sandbox and opens a pull request. Then it watches the live data to see whether the number moved, and after the goal is met it keeps watching in case the metric slips.

View more