Price a defined operational outcome and lifecycle, not “number of nodes” or guaranteed revenue. Discovery, build, integrations, security, testing, deployment, documentation, training, monitoring, changes, and incident support are distinct work.

// concept

Scope Before Price

Create a paid or bounded discovery artifact:

// prompt — copy me9 lines

current manual process and baseline
systems, owners, credentials, and APIs
event volume and peak behavior
data classification and compliance
happy/failure/recovery paths
acceptance criteria and exclusions
client responsibilities
license/hosting model
handover and support target

Unknown APIs, poor data, and unclear ownership are discovery risks—not free assumptions.

// concept

Build the Estimate

Estimate work packages and contingency based on evidence. Separate:

one-time discovery/build/migration/training;
recurring n8n/cloud/VPS/database/backup/monitoring;
third-party API, AI, messaging, and payment usage;
optional support/retainer with response scope;
taxes and currency terms under qualified advice.

Use milestone payments tied to demonstrable artifacts: approved design, staging acceptance, production handover, and stabilization. Define change control and out-of-scope rate.

// worked_example

Worked Example

A Karachi distributor requests “automate sales.” Discovery narrows it to form → CRM draft → human assignment, with no bulk marketing or automatic quoting. The proposal includes 12 acceptance tests, client-owned n8n/CRM accounts, training, 14-day stabilization, and an optional monthly monitoring plan.

PKR pricing shows original foreign infrastructure/API costs separately and states the exchange-date assumption. Global proposal uses contract currency and the same deliverables. Neither promises conversion uplift; it promises the tested workflow and support terms.

Acceptance also names which source systems and provider limits remain outside the consultant’s control, so operational responsibility is not disguised as a guarantee.

// failure_cases

Failure Cases to Diagnose

6 cases to diagnose

Fixed quote before API access
sell discovery or state assumptions.
Price per node
complexity/risk is not node count.
Third-party charges hidden
itemize owner and variability.
Unlimited support
define hours, incidents, response, changes.
Client credentials owned by freelancer
client creates production accounts.
Revenue guarantee
limit claims to measured operational evidence.

// pakistan_angle

Pakistan Angle

Local clients may compare automation with staff salary alone. Explain that the goal is reliable processing and evidence, not eliminating accountable people. Include PKT support windows, payment milestones, invoice/tax treatment, and foreign-currency volatility clearly.

For global clients, price risk, timezone coverage, data-processing terms, and payment fees. Do not underprice security and handover to win the project; those are the difference between a demo and a service.

// hands_on

Hands-On Exercise

5 steps

Create discovery brief for one client scenario.
estimate work and assumptions.
build one-time/recurring/usage/support price table.
define milestones, acceptance, and change control.
review license and ownership.

// completion_rubric

Completion Rubric

6 checks — tick as you verify

0/6

// sources

Sources

3 official sources — check every claim yourself

// check_yourself

Check yourself

4 questions · answers and options are taken word-for-word from this course

0/4

1 / 4 · diagnose
Your work shows this failure mode: “Unlimited support.” What does the lesson tell you to do about it?