LearnSynth Home ENPL
For companies only. VCPS runs only as a closed online edition, on request: 6–8 people from one organisation, your own projects, 20,000 PLN net per group.Terms for companies →
FLAGSHIP · LEARNSYNTH BY CATERPILLAR GARDEN

Value-oriented
Consulting Pre-Sales

Most projects don't fail in delivery. They fail in how they start.

Two days on how to talk to a client before the contract is signed: what actually has to happen, who decides it, and whether the project is worth taking at all. For IT teams who sell and run client projects — as a closed edition for one company, online live, on request.

Duration
2 days × 8h
Format
online live on MS Teams
Practice share
70% practice
Credential
LearnSynth certificate

Not sure this workshop is for your team? Email contact@caterpillar.garden or text +48 579 637 860 — I will answer honestly before you order.

Certified Practitioner — Value-oriented Consulting Pre-Sales
CLOSED EDITION · FOR COMPANIES

VCPS runs for companies — online, on request.

There are no open dates and no individual sign-ups. A company books the workshop for one team: online live on MS Teams, on a date agreed together. The terms are also on the page for companies.

THE PROBLEM

Every failed IT project has one thing in common: someone asked for requirements — instead of asking what actually needs to happen.

If you run or co-sell consulting projects, you'll likely recognise these patterns.

01

You enter the project blind.

You have a scope, but you don't know who actually made the buying decision, what the business goals of each stakeholder are, or what the client has already tried.

02

The scope came from an email — or AI.

Contradictions, unverified assumptions, promises nobody questioned in a live conversation. The project starts with a built-in defect.

03

There's no real sponsor.

The topic needs a board-level decision, but came in through a mid-level manager. Halfway through, the organisation asks: "why are you even here?"

04

Pre-sales knowledge is lost at handover.

Who is the key stakeholder, what were the real expectations, what had they already tried — all of it stays in the salesperson's head. Delivery starts blind.

05

We don't know where value is actually created.

We design solutions disconnected from the client's value streams and business reality. Result: an expensive feature no one needs.

06

Red flags only show after signature.

Blockers surface after the contract is signed — when the team has already sunk hundreds of hours, and stepping back hurts the most.

SOURCES

Buyers research with AI first and decide after talking to a person. In a Gartner survey of 645 B2B buyers, 69% validate AI-generated insights with a sales rep (Gartner, 2026 ↗). In the same research buyers were 32 percentage points more likely to say a rep — rather than GenAI — made them confident in the purchase decision (Gartner via Demand Gen Report, 2026 ↗). The edge is not access to information. It is the quality of that one conversation.

IS THIS FOR YOU

This workshop is for two different teams.

The programme is the same, but the problem looks different in a small advisory firm and in a larger IT organisation.

SMALL ADVISORY FIRM

Consulting boutique, team of advisors, small software house

You sell your own services and talk to the client yourselves. You have no large company brand behind you, so every proposal you write is your own unpaid time. If you want to stop billing by the hour, you need to be able to talk about what the client gets out of it.

  • You spot when to walk away — before you write the proposal, instead of waiting weeks for an answer.
  • You talk about the client's money — what the problem costs them today and what solving it is worth.
  • You have documents that look like they came from an advisory firm.
LARGER IT ORGANISATION

A team that starts projects at the client

The scope arrives by email, someone else runs the client conversations, and you have to deliver it. The workshop gives the sales people and the delivery people a shared language, so "that was not in the agreement" comes up less often.

  • Tech Team Leader, Engineering Manager — gets the project to deliver and needs to know what the client actually bought.
  • Solution Architect — sits in client conversations and writes the scope that later takes on a life of its own.
  • Pre-Sales Consultant, Technical Sales — wants to run the conversation from an advisor’s position.
  • IT Director, Head of Delivery — wants one standard where sales meets delivery.
  • Account Manager, BDM, Project Manager moving into an advisory role.

For this to make sense, you need

  • 2–3 years in IT: delivery, architecture, technical sales or management
  • at least one client conversation you have run about scope of work or a proposal
  • a real situation at work where you can practise the new tools within a month

You need no sales background at all. We teach that from scratch — the workshop is run by a practising consultant.

WHEN IT IS NOT WORTH IT

Five situations where your company's budget is better spent elsewhere.

I would rather write this now than explain it after the workshop.

  • 01

    You have no access to the client or to the person who signs the contract — and that cannot be changed. Every tool from the workshop assumes you talk to people on the client side.

  • 02

    In your company, sales decides on proposals and the technical side has no say. You would learn things you cannot use.

  • 03

    You expect two days to fix a process. They will not, until someone changes what people are rewarded for.

  • 04

    You are looking for a ready sales script or a certificate for your CV. Neither is here.

  • 05

    You have less than two years in IT and have not yet run a single client conversation about scope of work. Come back in a year — there will be something to work with.

If you recognise yourself in the first three points, write before you propose the workshop at your company: contact@caterpillar.garden or text +48 579 637 860. I will say honestly whether it is worth it, or whether something else should come first.

FREE TOOL

Take the list of questions, at least.

Ten questions that should be ticked off before a proposal leaves the company. Run it against the last proposal you sent and add up the score. The result shows in black and white what was skipped — and that is ready material for a conversation with your salesperson, or with whoever runs the client conversations. It usually ends one of two ways: either you get permission to fix it, or you come to the workshop together.

Download the checklist (PDF) ↓

No email required. It is one of the workshop worksheets, pulled out as a standalone tool — it works without the workshop.

WHAT CHANGES

What will actually be different when you come back.

Three levels. You will see the first within a week, the third after a few months.

THE MONDAY AFTER

What you do differently

  • You do not write a proposal until you can describe the client's problem in one sentence they have confirmed themselves.
  • You know who signs at the client, who can block the project, and what each of them has at stake.
  • You ask questions from a prepared list before you start proposing a solution.
AFTER A FEW CLIENT CONVERSATIONS

Who you become

  • You run the client conversation yourself instead of assisting someone else.
  • You hand the project over to delivery with a document both sides have read.
  • Sales people and delivery people describe the same project the same way.
AFTER A FEW MONTHS

What you stop losing

  • Weeks poured into proposals that never had a chance — you spot them earlier.
  • Rework after the project starts, because the assumptions were written down before anyone signed.
  • Projects you should walk away from — you leave in week two instead of week five.

The middle level depends on how much say you have in how your company talks to clients. If you have none, two days will not change that — which is why the list of situations where it is not worth coming sits above.

WHAT YOU'LL LEARN

After two days, you leave with a method and six completed documents.

Every block ends with an exercise on a real case. 70% practice, 30% theory — in small teams, around a working table.

01

Understand the client beyond the scope.

  • Map the decision-making structure: sponsor, champion, blockers
  • Identify business goals per position — before you start scoping
  • Recognise the client's value streams and where IT truly enters
  • Build an account plan grounded in strategy and political context
02

Discovery before proposal.

  • Run discovery conversations using diagnostic questions
  • Prepare and run micro-workshops as a scope-validation tool
  • Recognise usage scenarios — moments where the solution creates value
03

Red flags & qualification.

  • Spot warning signals early: bad message early is good message
  • Validate whether you're talking to someone who can and wants to decide
  • Step back or fix the situation before you sign
04

Documentation & handover.

  • Create structured pre-sales → delivery docs (Control Letter)
  • Order recommendations before writing a proposal — Proposal Prompter
  • Build Success Stories from delivered projects
05

A consultative approach to selling.

  • Apply quid pro quo — a two-way value exchange
  • Understand the 3 buying-process phases: Solution Development → Validation → Decision
  • Adapt your communication to the client's current phase
06

Shared language across sales–delivery.

  • Architects, leaders, and consultants speak the same language as sales
  • Less "that wasn't in scope" — more real collaboration
  • Business partner posture
WHAT YOU TAKE WITH YOU

Six tools you come back to on Monday morning.

This isn't a training for your CV. You leave with completed templates you apply immediately to a real project — your own or one from the workshop group.

✳ 01

Stakeholder Map (RPIAD)

A structured visual map of everyone in the project, categorised: responsible, participating, impacting, approving, deciding. No blocker or critical voice gets missed.

✳ 02

Goal Identification per Position

A framework for uncovering each stakeholder's real business goals in their role and context. Moves conversations from features to outcomes that actually matter.

✳ 03

Diagnostic Questions Bank

A curated set of questions designed to surface assumptions, constraints, and red flags early in the engagement. Diagnose before you recommend.

✳ 04

Control Letter — od ustaleń do realizacji

A lightweight document capturing agreed scope, key assumptions, sponsor, success conditions and known risks at the point of signing. Prevents knowledge loss at handover.

✳ 05

Proposal Prompter + 10-point readiness

A tool for structuring recommendations around three questions: why this solution, why us, why now. Plus a 10-point readiness check before submission.

✳ 06

Success Story Template

A template for building cases from delivered projects — both a sales and a reference asset. Turns delivered projects into company assets.

VCPS Training Set — case studies, worksheets, certificate and Certified Practitioner badge
TRAINING SET · SENT BY POST

A folder arrives at your desk by post.

  • Reveal deck — Nexatel (main case study)
  • Reveal deck — secondary case (different per group)
  • Completed worksheet example for the main case
  • 6 workbooks to fill in during the workshop
  • Certificate — online and printed
  • Badge as a sticker + LinkedIn graphic
  • LearnSynth by CG goodies
AGENDA

Two days × 8 hours, nine blocks, one coherent output.

30% theory · 70% practice

Closed edition, online live: two days, 9:00–17:00, on a date agreed with the company. The description written for buyers is on a separate page.

DAY 1 · 9:00–17:00

Understand the client

People, goals, value streams, discovery.

  • 9:00–9:30
    Opening — why are we here?
    Problem statement & workshop goals
  • 9:30–10:15
    Value-oriented framework in a nutshell
    CCS + value stream thinking in consulting
  • 10:15–10:30
    ☕ Coffee break
  • 10:30–12:00
    Block 1 · Stakeholder & value stream mapping
    → Org chart + value stream map on the case
  • 12:00–13:00
    🍕 Przerwa obiadowa
  • 13:00–14:15
    Block 2 · Goal Identification per Position
    → Position / Goal / Strategy table + account plan
  • 14:15–15:30
    Block 3 · Discovery conversation
    → Diagnostic questions + meeting plan, conversation simulation
  • 15:30–15:45
    ☕ Coffee break
  • 15:45–16:30
    Block 4 · Usage Scenarios
    → Completed usage scenarios on the case
  • 16:30–17:00
    Team presentations + Day 1 wrap-up
DAY 2 · 9:00–17:00

Secure the project

Red flags, documentation, handover, sales approach.

  • 9:00–9:30
    Day 1 recap
    Key takeaways, questions, alignment
  • 9:30–10:45
    Block 5 · Red flags & qualification
    → Red flags checklist · bad message early is good message
  • 10:45–11:00
    ☕ Coffee break
  • 11:00–12:30
    Block 6 · Control Letter & handover
    → Completed Control Letter pre-sales → delivery
  • 12:30–13:30
    🍕 Przerwa obiadowa
  • 13:30–14:30
    Block 7 · Proposal Prompter + 10-pt readiness
    → Completed Proposal Prompter
  • 14:30–15:15
    Block 8 · 3 phases of the buying process
    → Szukanie rozwiązania → sprawdzanie → decyzja
  • 15:15–15:30
    ☕ Coffee break
  • 15:30–16:15
    Block 9 · Quid pro quo + Success Stories
    → Completed Success Story from your own project
  • 16:15–17:00
    Final presentations + wrap-up
    → Full set of artefacts + Monday action list
TRAINER

Marcin Karkocha

Marcin Karkocha — Chief Technology Strategist, Founder of Caterpillar Garden
Marcin Karkocha
Chief Technology Strategist · Founder, Caterpillar Garden
About the trainer → Full credentials at marcin.karkocha.tech ↗

Nearly 20 years in enterprise IT — pre-sales, advisory, and delivery across Europe and Asia. Enterprise clients in financial services, manufacturing, and technology. Has led discovery engagements, built pre-sales frameworks, and closed complex consulting projects from first conversation to signed contract.

Creator of the Value-oriented Consulting Pre-Sales methodology — built from real deal cycles with corporate clients. Currently active in the London CTO community, CTO Academy, Flowtopia. Co-author, Routledge 2025.

Project experience · not training clients
IntelNordeaNokiaStandard CharteredSoftwareOnePlusCyfrowy Polsat
"Stakeholder Map, Control Letter, Red Flags — these aren't buzzwords. They're concrete work that helps you decide what's actually worth proposing to the client, and whether your firm should even be in this."
Maciej Kacprzak · Tech Lead, UNIQA ↗ LinkedIn
PRICING

One price per group, stated up front.

A closed edition for one company, online live. Net prices, the same as on the page for companies.

Format Group Price
Closed edition · standard
one organisation · online live on MS Teams · your own projects · 30-day follow-up
6–8 people
20,000 PLN net / group
Closed edition · extended group
the same method and the same schedule
9–10 people
individual quote
Tailored programme
wider scope, additional topics, deeper industry fit
group
+25–40% on the base rate

Prices are net; VAT invoice from ON Technologies Marcin Karkocha, with scope, dates and payment terms set out in the quote. Included: two days of live work, examples adapted to your industry, working materials (Stakeholder Map, Goal ID, Diagnostic Questions, Control Letter, Proposal Prompter, Success Story), a materials pack sent by post and a LearnSynth by Caterpillar Garden completion certificate for every participant, and an online follow-up session after 30 days.

HOW IT WORKS · CLOSED EDITION

Four steps from first call to follow-up.

  1. Brief
    Three minutes: who should be in the group, which industry you work in and what you want to change in client conversations.
  2. Quote and dates
    A quote and a proposed scope within 48 working hours. Dates agreed with you.
  3. Two-day workshop
    Online live on MS Teams, in English or Polish, worked on your real opportunities.
  4. Follow-up after 30 days
    An online session on what held up in practice, and certificates for participants.
ON REQUEST
Closed edition · online live on MS Teams · 6–8 people from one organisation · dates agreed together · quote within 48 working hours.
Fill in the brief ↗
QUESTIONS WORTH ASKING

FAQ

I have less experience. Is this for me?
Minimum is 2–3 years in IT (delivery, architecture, technical sales, or management). No formal pre-sales knowledge required — the training builds from the ground up, at the pace of experienced practitioners. Not sure if it fits? Let's do a 15-min call before you order.
What language is the workshop in?
Polish or English — the team decides. Working materials are bilingual PL/EN.
What do I need technically?
A computer with a camera and microphone, a stable connection, and MS Teams — the browser version is enough, no account needed. A second screen helps: Teams on one, working materials on the other. We work in small groups in breakout rooms, so having your camera on is part of the workshop.
How is it invoiced?
A VAT invoice to the ordering company from ON Technologies Marcin Karkocha (VAT ID PL7651606629). Scope, dates and payment terms are set out in the quote before the workshop.
How do I file a complaint?
Complaints go to contact@caterpillar.garden within 14 days of the workshop ending. We respond within 14 days. Full procedure: Terms.
What do I get after the workshop?
Completed templates from 2 days of work (Stakeholder Map, Goal ID, Diagnostic Questions, Control Letter, Proposal Prompter, Success Story), a LearnSynth by CG completion certificate, and a 30-day follow-up — a short online group session: what's working, what's next, what blockers remain.
Can I attend on my own, without my team?
No. VCPS runs only as a closed edition for one company: online live, on request, 6–8 people from one organisation. If you want to propose the workshop at your company, start with the company brief ↗ or show your manager the manager briefing (below). The description for buyers: VCPS for companies; terms and pricing: page for companies.
Are the sessions recorded?
No. Participants work on their real projects and talk about their own clients, so we do not record. You keep the filled-in templates, the materials and your notes.
How much time does this really take?
Two days of eight hours, then about an hour a week for four weeks after the workshop so that two tools become routine. Without that hour you keep the knowledge, but the way you work will not change.
ONE DECISION

Book an edition for your team and bring your own projects.

A closed edition, online live on MS Teams: 6–8 people from one organisation, 20,000 PLN net per group, dates agreed together, with a follow-up session 30 days later. Two days, six tools and a full set of completed documents the team takes back to work on Monday.

On the fence? Email contact@caterpillar.garden or text +48 579 637 860 — I will tell you whether this workshop answers your team's problem.