Przejdź do treści
Biblioteka skilli
Sprzedaż i obsługa klienta · Pisanie

client-proposal

/client-proposal

Pisze ofertę opartą na tym, co klient faktycznie powiedział: jego sytuację, zakres z wyłączeniami, odpowiedź na zastrzeżenia i opcje cenowe.

Repozytorium
agency-skills ↗
Licencja
MIT
Ostatnia zmiana repozytorium
04.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 04.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Pisze ofertę opartą na tym, co klient faktycznie powiedział: jego sytuację, zakres z wyłączeniami, odpowiedź na zastrzeżenia i opcje cenowe.

Wyzwalacze z opisu

I need a proposal out tonightrespond to this RFPwrite the SOWpitch document
Oryginalny opis (EN)

Use this skill when a proposal is due and it is about to be the last one with the name changed. Produces a proposal built from what the prospect actually said: their situation in their own words, the firm's named approach, scope with explicit exclusions, the objection they already raised answered directly, pricing options, and the proof the firm can stand behind. Also use for "I need a proposal out tonight", "respond to this RFP", "write the SOW", "pitch document".

Jak działa

  1. The play
  2. What good looks like
  3. Rules
Sekcje z nagłówków SKILL.md, w oryginale · 42 linii, 648 słów
Podgląd SKILL.md
---
name: client-proposal
title: Client proposal
description: |
  Use this skill when a proposal is due and it is about to be the last one
  with the name changed. Produces a proposal built from what the prospect
  actually said: their situation in their own words, the firm's named
  approach, scope with explicit exclusions, the objection they already
  raised answered directly, pricing options, and the proof the firm can
  stand behind. Also use for "I need a proposal out tonight", "respond to
  this RFP", "write the SOW", "pitch document".
category: Sales
tags: [proposals, rfp, scope-of-work, pricing, new-business]
---

Applies after a discovery call, when the firm knows what the prospect wants and has to put it in writing. Produces the proposal.

## The play

1. Write the situation section first, in the prospect's own language, before anything else in the document. If they said they were flying blind on what works, that sentence goes in, not "attribution challenges". This section is what makes the rest of the proposal land, and it is the one competitors skip. Everything after it is read more generously when the prospect recognises themselves at the top.

2. Name the approach using the firm's own methodology, with the firm's own names for its stages. A proposal that walks through this firm's named process is differentiated by default. One that walks through a generic four-phase engagement is interchangeable with every other proposal on the desk.

3. Answer the objection they already raised, early and in its own section. If they complained the last firm never reported, reporting gets addressed before the scope, not buried where they will miss it. The objection they volunteered is the thing they are actually buying against.

4. Scope the work: deliverables, how many, how often, who produces each. Then write the exclusions explicitly. Vague scope is what turns a signed deal into an unprofitable one by month three, and the exclusions section is where that is prevented.

5. Set the timeline against the prospect's stated deadline, with real milestones on real dates.

6. Build two or three pricing options with a genuine difference in scope between them, not the same work at three service levels. Price from what comparable engagements actually went for. A guessed price is either leaving money on the table or losing the deal, and both are expensive.

7. Add only proof the firm can stand behind: results with periods attached, clients confirmed as nameable. If nothing in the library fits, leave a marked gap rather than reaching for something adjacent. A result the prospect checks and finds overstated loses the deal and the referral.

8. Close with terms and one specific next step on a date. "Let us know your thoughts" ends a proposal with nothing happening.

## What good looks like

- First thing I check that most people skip: whether the document contains one sentence the prospect themselves said. If I can swap the name out and send it to somebody else, we have written a brochure and they will read it as one.
- The mediocre version: last quarter's proposal with the name replaced and the scope adjusted. It is faster, it is obviously faster, and it loses to whoever spent the extra hour on the situation section.
- I know it is right when the prospect quotes our own situation section back to us on the next call. That means they recognised themselves in it, and everything after that gets read generously.
- Second test: the scope has exclusions. A scope with nothing excluded means nobody has thought about month three, and month three is where the margin goes.
- Red flag: one pricing option. It forces a yes or no on the whole engagement instead of a conversation about shape, and it leaves the prospect nothing to negotiate with except the price.

## Rules

- MUST write the situation section in the prospect's own words, first.
- MUST use the firm's named methodology rather than a generic phase structure.
- MUST answer the objection the prospect raised, in its own section, early.
- MUST write explicit exclusions alongside the scope.
- MUST give pricing options a real difference in scope.
- MUST attach a time period to every result cited.
- MUST end with one dated next step.
- NEVER invent a client name, a metric, a case study or a price. Mark the gap and ask.
- NEVER name a competitor.
- NEVER open with a capabilities tour.

Wersje

W bazie nie ma innych skilli o nazwie client-proposal.

Migawka bazy z 13.11.2026 · wersja paczki a17f31858579 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100proposal-pricing
    Pomaga zbudować ofertę, ustrukturyzować cennik, przygotować SOW, wycenę i opcje cenowe dla klienta, a także przedstawić transakcję potencjalnemu nabywcy.
  • 100agency-proposals
    Pisze ofertę, SOW lub dokument pitchowy dla potencjalnego klienta agencji, z zakresem prac i wariantami cenowymi opartymi na wartości.
  • 90proposal-generator
    Tworzy profesjonalne oferty handlowe i wyceny dla małych firm, w tym SOW i odpowiedzi na RFP, z danymi nadawcy.
  • 100sales-proposal-writer
    Pisze ofertę B2B lub SOW, która opisuje problem kupującego jego słowami, wycenia koszt braku decyzji, przedstawia cenę jako opcje i wyznacza jeden następny krok z datą.
  • 100proposal-writer
    Pisze ofertę dla nazwanego klienta: jego sytuację jego słowami, 2 do 4 mierzalnych rezultatów, podejście przez wyniki faz, dostarczane elementy, harmonogram i inwestycję.
  • 90b2b-proposals
    Przygotowuje oferty B2B, zakres prac (SoW) i odpowiedzi na RFP z myślą o wygranej i kontroli rabatów.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.