For freelance developers & small agencies

Stop guessing what to say to software clients.

The practical client conversation data bank.

The Developer Sales Context helps you navigate discussion like a $250k VP of sales, engineering the bridge towards a signed contract

Get instant access — $79

Instant digital download
Word, Markdown, Excel & PDF
Works with ChatGPT, Claude, Gemini & similar tools

Example · price objection

ClientThanks for the proposal. The price is above our expectations. Can you reduce it?

Diagnose first

“Too expensive” can mean different things. What is it here?

BudgetScopeValueTiming

Your replyIs the constraint the total budget, the initial investment, or one part of the scope? I’d rather adjust scope or sequence than cut essential work and keep the same expectations.

Next step: a leaner first phase

Illustrative example based on the Core Playbook.

100+real conversations

600+pages

16annotated cases

17short scripts

21AI prompts

I sometimes overthink how to respond to clients, especially when pricing or project scope comes up. Having a reference to work from makes it easier to figure out what to say instead of starting from scratch.

I added all the context to my LLM, and my conversations with clients improved significantly. By the fourth day, I had closed $7,000 in business. I didn’t expect to see that kind of impact so quickly. It’s made a real difference in how I approach client conversations and use AI in my sales process.

Individual results vary. Not typical.

The problem

The chat is where projects get won, lost or stuck.

You can design the database, build the app and ship the release. Then a client questions your price, a brief arrives in one sentence, or a prospect stops replying. Nobody teaches this part, so most developers learn it by losing projects.

“That’s more than I expected.”

Decide whether to explain the value, adjust the scope, offer options or walk away.

“I want an app like this.”

Clarify assumptions, deliverables and the questions to ask before you estimate.

Your proposal gets no reply.

Review what was actually said before deciding whether, and how, to follow up.

A cheaper quote shows up.

Check whether scope, deliverables and assumptions are comparable before you react.

“Small” requests keep arriving.

Hold the scope with a change process, not an awkward argument.

A client wants to start small.

Define a first phase with clear deliverables, boundaries and the next decision.

Get the toolkit — $79

The hardest part of a silent prospect is not knowing what to do next. The examples helped me look at the conversation more objectively and think through my next move instead of sending another follow-up blindly.

The approach

Add 600+ page context for high conversion discussion instead of following generic AI sales advice.

Pitchstack is a library of real developer–client conversations on web, mobile, Shopify and software projects, turned into something you can use: annotated cases, a short playbook, proposal templates and prompts for your AI. You see what was said, what happened next and what to do differently, including the deals that were lost.

Real, not invented

Actual messages from actual projects between 2018 and 2024. Names, companies, contact details and links removed or replaced.

Honest about outcomes

Wins, losses and unknowns are labelled as such. No cherry-picked success stories, no guarantees.

Built for developers

Scope, estimates, SOWs, change requests and delivery moments, not generic sales theory.

What’s inside

Six pieces that work together.

Read it like a playbook, search it like a library, or give excerpts to your AI as context. Either way, you decide what gets sent.

Conversation Archive

600+ pages real client conversations from 2018 to 2025, anonymised. add to LLM, search or search for specific case scenario.

WordMarkdown

Core Playbook

The actual strategies and methods that work in the moments that matter: not a generic sales advice you get everywhere

WordPDF

Annotated Conversations

16 real cases: what was said, what happened, what worked, what to improve, and a reusable script. Outcomes labelled honestly.

WordPDF

Proposal & SOW Pack

Proposal, statement of work, milestone plan, change request and acceptance templates, plus an assumptions checklist.

Word

Case Study Template

Write case studies with problem, solution, timeframe and outcome, with links to your App Store, Google Play and GitHub work.

Excel

Reply Coach Prompt Pack

21 prompts and paste-ready instructions that turn ChatGPT or Claude into a reply coach built on the playbook.

WordMarkdown

Get all real world scenarios — $79

Unclear requirements can turn into difficult conversations later. The scope and proposal templates give me a better starting point for defining expectations before a project gets underway.

What you can do with it

Be better prepared for the conversations that decide projects.

Understand the message firstWork out what the client is really asking before you reply.
Quote without regretGive ranges with assumptions so estimates don’t turn into disputes.
Negotiate scope before priceOffer options instead of reflex discounts.
Follow up without sounding desperateShort, easy-to-answer messages that fit the actual conversation.
Protect your scope and your timeChange requests, boundaries and clean exits.
Stop staring at a blank reply boxStart from a real example and adapt it in your own words.

See a real case

This is how every case is annotated, losses included.

A client’s budget was far below the estimate. Here is what was said, what happened and what could be done differently.

REAL EXCERPT · ANDROID SPEECH-TO-TEXT PROTOTYPE · TRIMMED

DeveloperWould you be willing to share the budget range you have in mind for this project?

Client500–1000

DeveloperUnfortunately, that’s too low. I’m expecting at least 300 hours on the development of this app […] However, I’m willing to go at 2500 USD since I can see the potential in the app […]

ClientThank you for the proposal. I will go with someone else for this prototype. Will let you know if an opportunity for further collaboration comes.

Outcome

Lost: client chose someone else Evidence: stated in the conversation

What worked

Asked for the budget range directly instead of guessing.
Explained the number with hours and a rate, and made a visible concession.

What to improve

The gap was roughly 2.5× to 5×. A discount rarely closes a gap that large; a smaller first deliverable might.
The reasoning centred on the developer’s hours, not on what the client could test or learn.

Reusable script

With a budget of [range], I can’t responsibly deliver [full scope]. What I can deliver is [narrow slice] in [timeframe], which lets you test [key assumption]. If that works, we price the next phase after you’ve seen results. Would you like that option written up?

Get all real world scenarios — $79

Not every client conversation ends in a deal, and that’s exactly why I found the breakdowns useful. They give me a chance to think about what happened, what I could have handled differently, and what to try next time.

How this is different

Built around developer–client situations, not sales theory alone.

	Typical sales content	Pitchstack
Source	Invented role-plays and theory	Real developer–client conversations
Outcomes	Mostly success stories	Wins, losses and unknowns, labelled honestly
Built for	Salespeople in general	Developers: scope, estimates, SOWs, change requests
Format	Videos and lectures	Files you open, search and adapt in minutes
With AI	Not designed for it	AI-ready archive and a Reply Coach prompt pack
Promise	“Close more deals”	Better preparation. No guarantees.

Generic AI advice often misses the reality of dealing with software clients. Giving my LLM more relevant context has made its suggestions more useful for the conversations I actually need to handle.

How it works

Not a course. A toolkit you open when you need it.

No modules, no lectures, no eight-week program. When a client message lands, you open a file and get to work.

Find your situation

Price objection, vague brief, silent prospect, scope change or another client conversation.

See how it played out

Read a relevant example, its known outcome and the lesson, without assuming every case ends well.

Adapt and send

Use a script, or paste an anonymised message into your Reply Coach. Then make the reply your own.

Get instant access — $79

Who it’s for

Made for people who sell software development work.

A good fit

Freelance developers who sell their own work
Small agencies and studios
Technical founders who handle client acquisition
Developers using AI to help with client messages

Not a fit

Anyone looking for manipulation tricks or guaranteed results
People who want a video course or live coaching
Anyone expecting an AI subscription to be included

Client communication is a skill developers often have to learn on the job. Having practical examples and reusable starting points makes it easier to approach sales conversations more deliberately, rather than figuring everything out through trial and error.

Why this exists

Built from real project conversations.

Selling web, mobile and software work to clients over several years produced a long trail of conversations: price pushback, vague briefs, silent prospects, scope changes. They were never organised, so the lessons stayed buried.

Pitchstack turns those conversations into something you can open, search and learn from, with the losses left in. Names, companies, contact details and links have been removed or replaced, and outcomes are labelled only as far as the conversations show them. It is a reference and a set of starting points, not a promise of results.

FAQ

Questions, answered.

Is this a course?

No. There are no lectures or modules. It is a set of files you open when you need them: conversations, annotated cases, a playbook, templates and prompts.

What formats do I get?

Word (.docx), Markdown (.md), Excel (.xlsx) and PDF. The archive comes in Word and Markdown.

Are these real conversations?

Yes. They come from real freelance software projects between 2018 and 2024. Names, companies, contact details and links were removed or replaced with placeholders, and excerpts are trimmed where needed.

Are all the examples wins?

No, and that is the point. The cases include wins, losses, stalled deals and unknown outcomes, labelled honestly so you can learn from each.

How do I use it with ChatGPT or Claude?

The Reply Coach Prompt Pack gives you ready-made instructions and 21 prompts. You can also give your AI the annotated cases or selected archive excerpts as context. The full archive is large, so use a tool that handles large files, or load it in parts.

Will it help me win more clients?

It helps you prepare and respond more clearly. It cannot guarantee replies, sales or any client outcome. Results depend on your situation, your offer and your judgment.

Does it cover web, mobile, Shopify and SaaS projects?

Yes. The conversations cover mobile apps, web apps, e-commerce and software projects, plus related niches.

Are the contract templates legal advice?

No. They are general starting points. Have a qualified professional review any contract before you use it.

Is my client data safe if I use an AI tool?

Do not paste confidential client information into an AI tool without authorisation. Anonymise messages first and follow your client agreements and the AI provider’s data policies. The Reply Coach pack includes safe-use rules.

Is it only for freelancers?

It is built for freelancers, but small agencies and technical founders who sell development work can use it too.

What happens after I buy?

You get instant access to the files after checkout.

Ready when the next message lands

Next time a client pushes back, don’t start from a blank page.

Get 100+ real conversations, annotated cases, the playbook, proposal templates and AI prompts in one practical toolkit.

Get instant access — $79

Instant digital download · Word, Markdown, Excel & PDF

Instead of spending ages figuring out how to word a client reply, I now have examples and prompts I can refer to. It gives me a starting point and makes the process feel less like guesswork.