Qian Lin Web
Services / Email marketing

Email marketing.

Plan a clear email journey for enquiries, customers or subscribers, with permission, content and measurement requirements made explicit.

The job this service must do

Email should send relevant information to people with an understood relationship to the business. Consent, segmentation, timing and measurement are part of the design.

A useful first scope

What we define
and deliver.

  • Audience and message sequence
  • Template and automation requirements
  • Testing, consent and measurement checklist

List purchase, unsolicited outreach, copy volume, CRM migration and platform charges are excluded unless explicitly scoped.

Service coverage

What the work can include.

The final combination follows the project brief. Every included page, feature, integration and review point is named in the written scope before implementation.

01

Current state

Review the existing list and consent information, available evidence, ownership and the practical constraint the work must address.

02

Audience segments

Define the audience segments required for the agreed first scope and record what remains outside it.

03

Message sequence

Develop the message sequence through reviewable decisions and a defined list of outputs.

04

Automation handover

Prepare the automation handover and the files, checks or operating notes needed for handover.

Working process

From brief to a testable release.

The proposal names the review milestones. Timing depends on the number of pages and features, content readiness and third-party access.

Define the problem

Agree the audience, business goal, available list and consent information and the decision this project needs to improve.

Set the boundary

Name the consent boundary, required inputs, review points, exclusions and acceptance criteria.

Create and review

Work through a small number of reasoned directions, record feedback together and keep changes tied to the approved brief.

Prepare the handover

Check the agreed outputs, organise source files and document the next implementation or operating step.

Custom scope / USD

Custom quote

Custom Development. Final quote after scope.

A tailored website feature, application capability or internal tool. The first release is defined before quoting.

User accounts and business state move into application scope. Third-party licences extra.

Read all pricing boundaries ↗

Scope decisions

Questions to settle before build.

The proposal records confirmed requirements and lists any unknowns that need a separate, bounded review.

What is already approved?

Existing research, brand material, content, platform choices and account access should be separated from assumptions that still need a decision.

Who owns approval?

One named decision-maker and consolidated feedback prevent contradictory revision cycles and unclear acceptance.

What happens next?

The proposal identifies whether the work ends with a defined deliverable or continues into a separately scoped implementation.

Case study references

Reference studies
and interface details.

Each study identifies its public source, material status and the interface details being reviewed.

Explore working examples ↗
Can you use our existing subscriber list?

Only after ownership, consent, source and suppression requirements are understood. A list should not be treated as usable merely because it exists.

How milestones and handover work ↗

Frequently asked questions

Before you send the brief.

Can this be combined with website work?

Yes. When both are needed, the proposal sequences shared decisions and states which deliverables belong to each part of the project.

How many revisions are included?

The written proposal names the review stages and included revision rounds. Additional directions or production work are quoted before scope expands.

What do you need before starting?

A concise brief, the available list and consent information, the intended audience, one approval owner and any fixed platform, timing or compliance constraints.

Your next website

Have a website in mind?

Let’s talk about what it needs to do.
Share your brief. We’ll review the scope and reply in writing.