Playbook: custom offers

Target: 20-30% inbound → custom offer accepted на $1 500-3 500
Шаг 1: read inbound — 2-3 уточняющих вопроса в первом ответе чтобы выяснить real scope
Шаг 2: упаковать offer за 5-15 мин — base gig + upscale additions (tool use, RAG, streaming, observability, tests)
Шаг 3: отправить < 30 мин от inbound — first response wins, ranking учитывает response time
Шаг 4: negotiate — never просто снижать цену; value add вместо discount; scope reduction если bigger budget недоступен
Pricing формула: Tier A $500→$1.5-2.5K, Tier B $1.5K→$3.5-7K, Tier C $8K→$12-15K
Follow up через 3 дня + reminder за 1 день до expiration; после — let it go

Цель: конверсия inbound inquiry на high-value sale через custom offer с upscaled scope.

Base принцип: buyer который пришёл на $500 гиг уже prequalified. Главный барьер (выбор seller) уже пройден. Теперь задача — увеличить scope + цену до точки где это действительно полезно для buyer’а и прибыльно для Upready.dev.

Target conversion rate: 20-30% inbound → custom offer accepted на $1 500-3 500.

Что такое custom offer

Custom offer в Fiverr — отдельный mechanism отправки client’у специфического предложения с собственной ценой, scope, timeline. Не привязан к существующему гигу. Создаётся через Fiverr chat → “Custom Offer” button.

См. Термин: Custom Offers.

Шаг 1: read the inbound (первые 60 секунд)

Что buyer действительно говорит

Первое сообщение от buyer — почти всегда understated. Они пишут “hi, I’m interested in your Claude gig”, но hиже спрятано:

Real scope — почти всегда больше чем базовый гиг
Real timeline — часто urgent
Real problem — конкретная pain point, не generic “hey help me”

Твоя задача — draw it out уточняющими вопросами.

Уточняющие вопросы

Первое сообщение от seller должно содержать:

Acknowledge их запрос — “Yes, I can help with that”
Показать expertise — ссылка на relevant past work / proof
Ask 2-3 specific questions — чтобы понять real scope

Template:

Hi [Name]! Yes, we can add Claude AI integration to your Next.js app.
We've shipped similar work — here's one example: [Upready.dev
case study URL or gig screenshot].

Before I send you a scoped offer, I need to understand a couple things:

1. Is this an existing Next.js app or starting fresh? If existing —
   Next 14 or 15, App Router or Pages?
2. What's the main use case — chat assistant, code assistant,
   document Q&A, agent with tool use?
3. Do you need streaming, memory, tool calling, or RAG over your
   own documents?
4. Any deadline on your side?

Once I understand these — I can send you a custom offer with
exact scope and pricing.

Key: четыре уточняющих вопроса чтобы real scope выяснилось. Без этого — guessing, under-quoting или over-quoting.

Шаг 2: упаковать custom offer (5-15 мин)

Формула scope

Base gig scope (что входит в гиг как advertised) +

Upscale additions (что часто нужно но не включено):

Tool use / function calling
RAG over documents
Streaming
Error handling / retry logic
Observability (Langfuse, LangSmith, custom)
Type safety
Tests / eval suite
Documentation
Deployment help
Handover call
Post-delivery support window (7-14 days)

Формула pricing

Tier A gig: $500 base → $1 500-2 500 upscaled offer Tier B gig: $1 500 base → $3 500-7 000 upscaled Tier C gig: $8 000 base → $12-15K upscaled

Justification scheme:

“Your use case involves [specific complexity]” (production app, not demo)
“Production-grade implementation includes [list]”
“For your [industry], [security/compliance] is critical”
“Timeline pressure means [better architecture upfront]“

Structure custom offer в Fiverr

Поля Fiverr Custom Offer form:

Title: краткое описание (60 symbols max)
Description (main): detailed scope, deliverables, approach
Price: USD number
Delivery time: days
Revisions: 2-3 (not unlimited)
Expiration: 7 days по умолчанию

Custom offer template

Title: Production Claude integration for [their product name]

Description:
Custom scope for your [their specific situation] — production-grade
Claude AI integration in your Next.js app.

Deliverables:
- [Bullet 1] — e.g., "Claude chat widget with streaming SSE"
- [Bullet 2] — e.g., "Tool use: can query your Supabase via RPC"
- [Bullet 3] — e.g., "RAG over your /docs folder with vector search"
- [Bullet 4] — e.g., "TypeScript types + error handling"
- [Bullet 5] — e.g., "Monitoring via Langfuse"
- [Bullet 6] — e.g., "30-minute handover Zoom call"
- [Bullet 7] — e.g., "7-day post-delivery bug fix window"

Tech stack:
- Anthropic Claude API (claude-3-5-sonnet-20250101 or latest)
- Next.js 15 App Router
- TypeScript strict mode
- shadcn/ui for chat components
- Prompt caching optimization

Not included (priced separately if needed):
- Vector DB setup (if existing infra not suitable)
- UI/UX redesign beyond component styling
- Multi-language support

Delivery: 7 days
Revisions: 2 included
Price: $2,500

Критично:

Каждый bullet — конкретен, не generic
“Not included” секция защищает от scope creep (см. scope-creep playbook)
Tech stack показывает quality signal

Шаг 3: отправить + мониторить

Отправить через Fiverr chat

Response time target: < 30 минут от inbound message до custom offer sent.

Почему критично:

Buyer ищет активно — у него множество tabs открыто
Первый response wins — даже если не самый дешёвый
Fiverr ranking учитывает response time (badge “Responds within 30 min”)

После отправки — message:

"Just sent you a custom offer. Key points:
- Scope: [2-line summary]
- Price: $X
- Timeline: Y days

If anything doesn't match your needs — tell me what to adjust and
I'll revise. Offer expires in 7 days."

Зачем: re-engage buyer, summary легче читать чем offer body, reduces friction to accept.

Шаг 4: negotiate если нужно

Possible reactions

A. Accept immediately (10-15% случаев)

Buyer принимает сразу — start work.

B. Counter на lower price (30-40% случаев)

Strategy 1 — hold firm:

"I understand, but the pricing reflects the production-grade scope we
discussed. If you need a smaller budget, I can reduce scope:
- $1 500: [less features, e.g., no RAG, no monitoring]
- $1 000: [minimal MVP, e.g., just chat widget with streaming]

Let me know which fits."

Strategy 2 — value add instead of discount:

"Instead of discount, I can include [extra deliverable] at same price:
- Free 30-day post-delivery support (worth $500)
- Extra revisions (3 instead of 2)
- Free 1-hour consultation after delivery

Which would help most?"

Never: просто снижать цену. Подрывает positioning и создаёт precedent для всех следующих clients.

C. Questions about scope (30% случаев)

Нормально. Answer specifically и offer to revise scope если needed. Не защищаться.

D. “Let me think” / no response (20-30% случаев)

Follow up через 3 days:

"Hey, just checking in. Offer expires in [X] days. If you're still
evaluating, happy to discuss any questions or tweak the scope.
If not the right fit, no worries — just let me know so I know."

Second follow up через 5 days (ONE day before expiration):

"The offer expires tomorrow. Last chance — want me to adjust scope
or extend timeline? Otherwise I'll assume not a fit and we can
revisit later."

После expiration — let it go. Не re-engage если нет signal.

E. Ghost / accept but delay payment

Normal — 20% buyers просто disappear. Не тратить energy.

Примеры custom offers (real-world)

Example 1 — Claude integration upscale

Inbound: “Hi, I saw your $500 Claude gig. I have a small Next.js app and want to add a chatbot.”

Уточняющие вопросы → buyer отвечает:

Next 15 App Router
Support chatbot for their SaaS (e-commerce analytics)
Нужен context от user’s data в Supabase
Timeline: hard deadline в 2 weeks

Real scope:

Chat widget (advertised in $500 gig)
+ Tool use to query Supabase (buyer’s data = tool call)
+ Streaming for better UX
+ Supabase RLS check в tool handler (security)
+ Type safety + error handling
+ Langfuse observability
+ Post-delivery handover + 7-day fix window

Custom offer: $2 500, 10 days, 2 revisions.

Result (typical): ~25% acceptance rate at this price point, assuming good fit.

Example 2 — Supabase RLS audit upscale

Inbound: “Need help with Supabase permissions, looks like RLS is broken.”

Уточняющие вопросы → buyer отвечает:

Production SaaS в active использовании (not demo)
12 tables
Multi-tenant architecture (critical for their business)
Recently failed pen test

Real scope:

RLS audit (advertised in $400 gig)
+ Full production rewrite (не просто report)
+ Test suite for все permission paths
+ 30-day monitoring setup
+ Incident response plan
+ Documentation для их team

Custom offer: $3 000, 14 days, 3 revisions.

Шаг 5: accept → kick off project

После accept:

Thank buyer в chat, confirm timeline
Request access — GitHub, Supabase, Anthropic key, design files
Set up project в internal Notion (tech team brief)
Tech team starts work async
Daily updates в Fiverr chat (“progress update — done X, working on Y, ETA Z”)
Deliver через Fiverr submit (не email / GitHub private link без notification)

KPI custom offers (месяц 1)

Метрика	Target
Inbound inquiries на week	3-5
Custom offers sent	2-3 per week
Acceptance rate	20-30%
Avg custom offer value	$1 800-2 500
Orders from custom offers	1-2 per month
Gross revenue	$2 000-5 000

Это главный канал рокет-fuel для premium pricing без organic traffic.

Что делать если…

Inbound только на low-budget

Симптом: все inbound inquiries — “I have $50-100, can you do X”.

Диагностика: positioning в гиг description недостаточно premium, или attracting wrong audience через Tags / Keywords.

Fix:

Review gig titles — убрать anything sounding “cheap” (“quick”, “simple”, “basic”)
Remove tags типа “budget” / “cheap”
Highlight “enterprise” / “production” / “premium” в description
Raise Basic tier price (если $400 привлекает tire-kickers, set $800)

Custom offers never accepted

Симптом: 10+ custom offers sent, 0 accepted.

Possible causes:

Price слишком high для market
Scope unclear, buyers не понимают value
Competition (buyer compared и выбрал cheaper)
Buyer seriousness — просто info-seeking