Skip to content

Complete fictional project

Follow a Freelance Project: From First Contact to Final Payment

Follow Sam of Harbor Street Bakery and Jordan Lee Studio through one fictional website engagement. Every stage shows the shared record, the freelancer’s decisions, the client’s responsibilities, and the documents that keep the project understandable.

19 connected stagesBoth perspectives$6,800 reconciled project ledgerUseful without AI

Fictional project record

Harbor Street Bakery at a glance

People
Sam, owner and approver, works with Jordan Lee of Jordan Lee Studio.
Original scope
Five responsive pages, a catering form, analytics handoff, editor access, and an update guide.
Approved change
HSB-WEB-01-CR02 adds Wedding Catering and Corporate Catering pages and moves launch to December 2, 2026.
Price
$5,600 original fee plus $1,200 approved change, for $6,800 total.
Payment ledger
DateTriggerAmountStatus
October 15, 2026Base milestone 1 — kickoff and structure$1,400Paid
October 24, 2026Base milestone 2 — design direction approved$1,400Paid
November 7, 2026Change milestone 1 — CR02 approved$600Paid
November 18, 2026Base milestone 3 — staging accepted$1,400Paid
December 5, 2026Base handover ($1,400) plus accepted CR02 work ($600)$2,000Paid December 12
Project total$6,800Paid in full

You can read the entire walkthrough without using Lucy. Tool links open the existing blank tool for that project stage; no example or user information is transmitted merely by following a link. If you choose to submit text, remove names, credentials, account details, and unnecessary confidential information first. Read how requests are handled.

01

Sam identifies a business need

The project starts with a problem customers and staff can observe, not a feature list or a promised business result.

Fictional timeline · October 1, 2026

Harbor Street Bakery’s one-page site makes product and catering information difficult to find on a phone. Customers call for answers, and Sam wants a clearer inquiry path before the holiday catering campaign.

Sam describes the need and known inputs, then asks Jordan whether the work appears aligned. The inquiry leaves page count and form details open for discovery.

Freelancer perspective

What Jordan is working through

  • Decide whether the broad need fits your service, capacity, and ethical boundaries.
  • Avoid confirming a price, schedule, or solution before the dependencies are understood.

Client perspective

What Sam is working through

  • Explain what is difficult now, who is affected, and why the timing matters.
  • Share known constraints while leaving room for the freelancer to ask questions.

02

Sam turns the need into a bounded brief

A useful brief gives candidates the same starting facts without pretending every technical decision is settled.

Fictional timeline · October 3, 2026

Sam records five expected pages, the catering form, supplied assets, a $6,000 planning ceiling, the target date, exclusions, and Sam’s role as final approver.

The brief labels open hosting and content-system questions instead of hiding uncertainty.

Freelancer perspective

What Jordan is working through

  • Use the brief to identify assumptions, missing dependencies, and work that may need a specialist.
  • Do not treat the client’s planning ceiling as proof of the correct project price.

Client perspective

What Sam is working through

  • Name tangible outputs, important exclusions, supplied inputs, and the person who can approve.
  • Keep passwords, customer data, and account details out of the brief.

03

Jordan evaluates fit before promising

The freelancer’s first decision is whether to continue the conversation, not how quickly to close the work.

Fictional timeline · October 6, 2026

Jordan checks service fit, availability, the likely skills involved, Sam’s decision authority, and risks around content, access, ecommerce assumptions, and the holiday date.

The project appears potentially suitable, but discovery must confirm the actual pages, form behavior, handover, and review process.

Freelancer perspective

What Jordan is working through

  • Identify what would make the project unsuitable or require a referral, partner, or different schedule.
  • Respond with focused next steps rather than a premature fixed quote.

Client perspective

What Sam is working through

  • Expect relevant questions. They are part of responsible evaluation, not evidence that the freelancer is difficult.
  • Use the response to assess whether the freelancer recognizes constraints and uncertainty.

04

Both sides test the assumptions

Discovery turns an attractive idea into information that can support scope, price, timing, and responsibilities.

Fictional timeline · October 8, 2026

Sam and Jordan clarify the audience, five initial pages, form purpose, content readiness, access, approval, accessibility checks, handover, and excluded ecommerce/payment work.

Campaign landing pages are explicitly outside the first release. That detail later makes the change discussion concrete.

Freelancer perspective

What Jordan is working through

  • Ask about the business process around the deliverable, not only visual preferences.
  • Record assumptions and open items so the proposal does not silently fill gaps.

Client perspective

What Sam is working through

  • Bring the person who can decide and say honestly which inputs are not ready.
  • Confirm how staff will operate the result after handover.

05

Jordan proposes one testable approach

The proposal connects Sam’s need to a defined approach rather than presenting a price without boundaries.

Fictional timeline · October 10, 2026

Jordan proposes the five-page site, form, handover, four $1,400 base milestones, November 21 target, client responsibilities, included revision rounds, and explicit exclusions.

The proposal states that timing depends on agreement approval, inputs, and review dates.

Freelancer perspective

What Jordan is working through

  • Tie the fee to the described work and surface assumptions that could change it.
  • Explain what creates an agreement and what must move into the SOW.

Client perspective

What Sam is working through

  • Compare the proposal against the brief and discovery notes, not only the total.
  • Look for missing outputs, expenses, dependencies, acceptance, and close-out.

06

Sam asks about the terms that affect use

A useful proposal review turns broad phrases into shared decisions before they harden into an agreement.

Fictional timeline · October 13, 2026

Sam asks who owns hosting accounts, what one revision round means, which accessibility checks are included, and what support follows launch.

Jordan answers specifically and agrees to carry the clarifications into the SOW.

Freelancer perspective

What Jordan is working through

  • Answer the actual question and revise ambiguous wording instead of relying on reassurance.
  • Do not dismiss operational, accessibility, rights, or security questions as boilerplate.

Client perspective

What Sam is working through

  • Ask how an important promise will be observed or recorded.
  • Distinguish required project decisions from optional enhancements.

07

Both sides make the boundary visible

Scope is easier to manage when deliverables, exclusions, responsibilities, and shared decisions appear in the same record.

Fictional timeline · October 15, 2026

The scope matrix names the five pages and handover items, excludes ecommerce and campaign pages, and assigns inputs, feedback, testing, and approval responsibilities.

It also distinguishes Jordan’s work from decisions both sides must approve together.

Freelancer perspective

What Jordan is working through

  • Check that the scope matches the work you estimated and can actually deliver.
  • Name third-party and client dependencies rather than absorbing them into an optimistic schedule.

Client perspective

What Sam is working through

  • Confirm that the described outputs match the business need and available internal work.
  • Do not assume adjacent features are included because they seem related.

08

They connect money to observable project events

A milestone is useful when both sides can tell what event triggers review and payment.

Fictional timeline · October 15, 2026

The SOW records four $1,400 base milestones: kickoff/structure, design approval, staging acceptance, and final handover. It also names review expectations, acceptance checks, change handling, rights/security prompts, and close-out.

The original fixed fee is $5,600 USD. The later change is not part of this starting amount.

Freelancer perspective

What Jordan is working through

  • Make cash-flow and work-start assumptions explicit.
  • Use observable outcomes rather than vague percentages or calendar dates alone.

Client perspective

What Sam is working through

  • Reserve time to review each milestone and understand when payment is triggered.
  • Check that the milestone evidence is proportional to the payment decision.

09

Approval identifies the controlling record

A clear approval says who accepted what, through which method, and what must happen before work starts.

Fictional timeline · October 15, 2026

Sam and Jordan identify the SOW, controlling agreement, and clarification record. They confirm authority and the first milestone trigger.

They also preserve the rule that material changes need a recorded decision rather than an informal suggestion.

Freelancer perspective

What Jordan is working through

  • Confirm the approved version and required payment or access conditions before beginning.
  • Preserve the record in the agreed project channel.

Client perspective

What Sam is working through

  • Verify the final documents match the last conversation and that the approver has authority.
  • Do not rely on silence or an outdated proposal version.

10

Jordan starts with a shared operating record

Kickoff is where the written project becomes a working routine for decisions, inputs, status, and access.

Fictional timeline · October 15–17, 2026

Jordan records the communication channel, weekly status day, approval authority, decision-log rule, and next review. Sam supplies content and access securely by October 17.

No credential is copied into the project documents.

Freelancer perspective

What Jordan is working through

  • Confirm received inputs, access boundaries, next decision, and known blockers.
  • Use written recaps so later work is not reconstructed from memory.

Client perspective

What Sam is working through

  • Provide only the access needed and use organization-owned accounts where practical.
  • Verify that the freelancer received usable, approved material.

11

Sam supplies decisions; Jordan reports progress

Delivery depends on both sides completing the responsibilities attached to the work.

Fictional timeline · October 17–November 4, 2026

Sam supplies approved materials and gives one consolidated design response. The key-page design is approved October 24, triggering the second $1,400 base milestone.

Jordan’s November 4 update separates completed work, current work, decisions, and a possible request for two landing pages.

Freelancer perspective

What Jordan is working through

  • Report progress and emerging risks before the schedule is in danger.
  • Record a possible new request as unapproved until the baseline comparison is complete.

Client perspective

What Sam is working through

  • Consolidate stakeholder feedback and answer the requested decision, not every possible preference.
  • Acknowledge how late or changed inputs affect dependent work.

12

Sam asks for two additional landing pages

The request is reasonable to discuss, but it is not automatically included merely because it supports the same website.

Fictional timeline · November 6, 2026

Sam asks for separate Wedding Catering and Corporate Catering pages after the original design direction is approved. Jordan compares the request with the five named pages and the explicit campaign-page exclusion.

They discuss the audience, supplied copy, navigation, testing, price, timing, and whether anything should be removed or deferred.

Freelancer perspective

What Jordan is working through

  • Do not begin the added work while the impact is still being negotiated.
  • Distinguish a requested addition from a correction needed to meet the existing agreement.

Client perspective

What Sam is working through

  • Explain the new need and priority rather than assuming the existing fee covers it.
  • Consider adding, swapping, deferring, or declining work based on budget and timing.

13

CR02 changes price, schedule, inputs, and acceptance

A useful change record explains more than the added fee: it shows what work, dates, responsibilities, and checks move.

Fictional timeline · November 7–8, 2026

Sam and Jordan approve two added pages for $1,200: $600 on change approval and $600 after acceptance. The launch moves from November 21 to December 2.

Sam supplies copy and images by November 8; feedback remains due within three business days. The original SOW continues except where CR02 changes it.

Freelancer perspective

What Jordan is working through

  • Check authorization and the first change-payment trigger before beginning.
  • Update the working plan and final invoice logic, not only the scope list.

Client perspective

What Sam is working through

  • Confirm the budget and schedule effect before approval.
  • Meet the new input deadline so the revised launch remains realistic.

14

Jordan delivers the seven-page project

A delivery message should make the review task clear instead of simply announcing that the work is done.

Fictional timeline · December 2, 2026

Jordan delivers the five original pages, two CR02 pages, form, analytics handoff, editor access, source assets, license list, update guide, and backup record.

The delivery note restates the agreed checks and asks for one consolidated response.

Freelancer perspective

What Jordan is working through

  • Enumerate every output and where it can be reviewed or retrieved.
  • Distinguish final delivery from an informal preview and preserve submission evidence.

Client perspective

What Sam is working through

  • Review against the original SOW plus CR02, not memory or unrelated new preferences.
  • Use the agreed environment and report issues specifically.

15

One defect is corrected; one new idea is parked

A precise review separates a failure against agreed criteria from a new feature request.

Fictional timeline · December 4, 2026

Sam reports that the form confirmation is not exposed correctly on an agreed mobile browser and supplies reproduction steps. Jordan confirms it is a correction and fixes it within the included round.

Sam also asks about online deposits. Both sides record that as future work because ecommerce and online payments are excluded.

Freelancer perspective

What Jordan is working through

  • Acknowledge a reproducible defect and correct it without reframing it as paid scope.
  • Record the separate new idea so it is not lost or confused with acceptance.

Client perspective

What Sam is working through

  • State the environment, steps, actual result, and expected result.
  • Do not hold accepted work open for an excluded enhancement.

16

Sam accepts the recorded deliverables

Written acceptance identifies what passed, what was corrected, and what is not an outstanding item.

Fictional timeline · December 5, 2026

Sam confirms the seven pages, form, agreed checks, handover items, and December 4 correction. The acceptance message explicitly leaves online deposits as future scope.

The message asks Jordan for a final invoice showing prior payments and the two remaining amounts.

Freelancer perspective

What Jordan is working through

  • Preserve the acceptance record and confirm the next close-out steps.
  • Do not bundle portfolio or testimonial permission into project acceptance.

Client perspective

What Sam is working through

  • Confirm completion in the form required by the agreement.
  • List any real outstanding item; do not rely on silence to close the project.

17

Jordan reconciles the complete payment record

The final invoice makes the base fee, approved change, prior payments, and remaining balance easy to verify.

Fictional timeline · December 5, 2026

Jordan invoices $2,000: the $1,400 base handover milestone plus the remaining $600 CR02 installment. The invoice shows $4,800 already paid and a $6,800 total project value.

Payment instructions remain in the approved secure channel, not the public project document.

Freelancer perspective

What Jordan is working through

  • Match line items and triggers to the SOW, change request, and acceptance record.
  • Show prior payments so the client can reconcile the balance without reconstructing the project.

Client perspective

What Sam is working through

  • Verify the project reference, amounts, prior payments, payee, currency, and internal routing requirements.
  • Resolve an arithmetic or record question promptly rather than leaving the invoice unacknowledged.

18

Sam pays and both sides update the ledger

Payment completion is a recordable project event, not an assumption based on sending an invoice.

Fictional timeline · December 12, 2026

Sam processes the $2,000 invoice under the agreed term. Jordan records receipt. The ledger now shows $5,600 in base payments and $1,200 under CR02, totaling $6,800.

Neither side publishes payment credentials or sensitive account details in the educational record.

Freelancer perspective

What Jordan is working through

  • Acknowledge receipt and update the project balance.
  • Retain the invoice/payment record according to the business’s actual administrative requirements.

Client perspective

What Sam is working through

  • Retain the approved invoice and payment evidence with the project record.
  • Keep tax and vendor documentation in the organization’s appropriate secure system.

19

They close access, records, and future-work boundaries

A clean close protects both parties by confirming operational ownership and separating future work from the finished engagement.

Fictional timeline · December 13, 2026

Sam verifies bakery-owned accounts, documentation, files, licenses, analytics, and the backup. Jordan reduces temporary access after verification.

The correction window, future-work process, and portfolio permission are recorded separately. No testimonial or referral is assumed.

Freelancer perspective

What Jordan is working through

  • Leave the client able to operate the delivered work and remove access you no longer need.
  • Ask for portfolio, testimonial, and referral permission as separate choices.

Client perspective

What Sam is working through

  • Verify access and recovery ownership before the freelancer leaves.
  • Know which post-launch issues are included corrections and which require a new project.

Keep going

Freelancer pathway

Build the process from your side

Define a service, respond to inquiries, estimate, propose, deliver, invoice, and close deliberately.

Client pathway

Prepare and manage a first hire

Turn a business need into a brief, compare proposals, provide feedback, accept work, and close access.

Reusable documents

Open the template library

Copy blank project briefs, proposals, SOW outlines, change requests, invoices, and handover checklists.