Should I show my process on my website?
Yes, for almost all service businesses — and the reason is psychological, not tactical. The single biggest source of pre-purchase anxiety for high-ticket services is not price; it's uncertainty about what happens after you say yes. A prospect who can read your 4-step process and think 'oh, that's manageable — discovery call, proposal, design, launch — I can do that' has had their anxiety resolved before they even reach out. Without a process section, prospects either carry that uncertainty into the enquiry (making your discovery call do more work) or they don't enquire at all. The process section does conversion work that no testimonial or case study can replicate.
How many steps should a process section show?
3 to 5 is the optimal range — the sweet spot between 'this feels too simple' and 'this feels complicated.' Fewer than 3 steps raises questions about whether the process is rigorous enough for a serious project. More than 5 starts to feel complex and overwhelming, which is exactly the opposite of what a process section should do. If your actual process has 8 stages, group related stages into 4 phases. The goal is to give the prospect confidence and clarity, not to document every step for internal operations. Your contracts, onboarding documents, and project management system contain the full detail — the website shows the shape of the journey.
Where should the process section go on the page?
On a services page: after the service description and outcomes, before testimonials and the CTA. This sequence works because the visitor has first understood what the service is and what they get — then the process section shows how you deliver it, answering 'what happens next?' at the exact moment they're asking it. On a homepage: usually mid-page after an initial services overview, though for most service businesses a brief 3-step summary on the homepage with a 'see full process' link to the service page works better than a detailed process section in the homepage flow.
How to present your process on your website is one of the most underestimated conversion decisions a service business makes. A prospect who finds your work compelling but can't picture what the engagement looks like will hesitate — or choose a competitor who removes that uncertainty. A clear, specific process section does more conversion work in 100 words than most businesses realise.
This guide covers step count, naming, placement, copy, and the mistakes that turn a potentially powerful process section into generic noise that no visitor remembers.
Why Does Showing Your Process Reduce Friction?
The hesitation most people feel before enquiring about a high-ticket service isn't primarily about price — it's about the unknown. They don't know what "getting started" actually means. Will there be a long onboarding? Will they need to provide hours of content? Will they be locked in before they know whether you're the right fit? This is the same anxiety that website contact page best practices addresses through headline copy and expectation-setting paragraphs — uncertainty is the enemy of action at every stage of the funnel.
A process section answers all of those implicit questions before they become spoken objections. When a prospective client in London, Toronto, or Sydney reads your 4-step process and thinks "oh, that's straightforward — discovery call, proposal, design, launch — I can do that," their hesitation drops significantly.
The secondary benefit is professionalism signalling. A clear, named process says you've done this many times before, that the engagement has a defined structure, and that a client won't end up in a chaotic, open-ended situation. This matters particularly for clients who've had bad experiences with freelancers or agencies that had no clear process at all. That professional credibility is exactly what what makes a website look trustworthy is built from — visible systems that say "we know what we're doing."
How Many Steps Should Your Process Have?
3 steps — works for very simple or fast services. "Discovery → Design → Deliver" is clean and decisive. The risk: it can feel oversimplified for complex services, and raises the question "what exactly happens in each of those phases?" — which is why a well-written website FAQ page often handles the follow-on questions that a 3-step process leaves unanswered.
4 steps — the most common and often the best choice. Provides enough structure to feel rigorous without feeling complex. "Discovery → Proposal → Build → Launch" covers a full project cycle cleanly and gives the prospect a clear mental journey.
5 steps — works for services with a natural 5-phase cycle. "Brief → Research → Design → Review → Deliver" for a brand identity project, for example. Beyond 5, visitors start to feel like the project will be complicated and they'll lose track of where they are.
More than 5 — group them. If your web design process genuinely has 8 stages, present them as 4 phases of 2 stages each: "Phase 1: Discovery & Planning (1 week). Phase 2: Design (2–3 weeks, 2 rounds of revisions). Phase 3: Development & Testing (1 week). Phase 4: Launch & Handover (3 days)." The grouping preserves completeness while keeping the visual presentation clear.
What Should You Name Each Step?
The names of your process steps are more important than the detailed descriptions. They need to communicate what happens in that phase and sound reassuring rather than bureaucratic.
Effective step names:
- "Discovery" or "Strategy Session" — clear that it's a conversation, not a deliverable
- "Proposal" or "Scoping" — sets expectation of a defined proposal before any commitment
- "Design" or "Build" — the work phase, named plainly so it's immediately understood
- "Review" or "Refinement" — signals client involvement and revision opportunity
- "Launch" or "Handover" — completion, clear endpoint, closure
Avoid naming steps with internal jargon — "ideation phase," "stakeholder alignment," "creative exploration" — or overly corporate language: "commencement of engagement," "final deliverable submission." A prospective client in Sydney or New York should be able to read your process step names and immediately understand what each phase involves. If they need a dictionary, the section is doing the opposite of its job.
This naming clarity is also why how to write website copy treats plain language as a conversion asset, not a stylistic preference — every piece of jargon that a visitor has to decode is a moment of friction.
What Should Each Step Description Say?
Each step description should answer three things in 2–4 sentences: what happens in this step, what the client's role is, and how long it takes.
The client involvement detail is what most businesses leave out — and it's what creates the clearest mental picture. A prospective client thinking "but what do I actually need to do?" gets the answer before they have to ask.
Example step description for a "Discovery" phase:
"We start with a 45-minute video call to understand your business, clients, and goals. You'll share any existing brand materials or website feedback you have. We use this session to scope the project and confirm we're the right fit before proposing anything. Scheduled within 3 business days of your enquiry."
That description does four things: explains the activity, names the client's contribution, sets a timeframe, and removes uncertainty about commitment. That's the template for every step.
Where Does the Process Section Go on the Page?
On a service page: After the description and outcomes, before testimonials and the CTA. The sequence works because: first the visitor understands what the service is and what they get; then the process section shows how you deliver it; then testimonials prove you've delivered it for others; then the CTA captures the enquiry. Change that order and each section does less work.
On a homepage: Usually not in the main flow unless your process is a genuine differentiator worth featuring early. A brief 3-step summary on the homepage with a "see full process" link to the service page works better than a detailed process section in the homepage flow — it gives enough to reassure without consuming space that should be showing results and proof.
On a dedicated "How We Work" page: Worth creating if your process spans multiple services and you get repeated questions about it. This page can be linked from the FAQ page — "How does a project typically work?" — and from the contact page — "Not sure what to expect? Read about our process."
What Should You Avoid in a Process Section?
Vague step names with no substance. "Discovery → Design → Deliver" with no descriptions is slightly better than nothing — but only slightly. If you're going to have a process section, put real content in each step.
Excessive steps that imply complexity. Eight steps creates the impression that working with you is complicated. The visitor is running their own business alongside this engagement. Complex process equals complex project. Simplify the presentation even when the underlying process is thorough.
No timeframes. A process with no timeframes is one of the most common missed opportunities. "Proposal sent within 3 business days of the discovery call" and "Design phase: 2–3 weeks" are the specific promises that build confidence. Without timeframes, the process is just a description — not a commitment that the prospect can plan around. The specific numbers that make a process credible are the same ones that make website copy convert — vague claims are ignored; specific claims are evaluated and trusted.
Process as the only differentiator. "We listen carefully, then we design, then we deliver" is not a differentiator — it's a description of what every agency does. Your process section should include the specific details that make your process yours: what you produce at each stage, what makes your discovery session better, what the client gets at the end of each phase.
Real Examples of Process Section Copy That Works
Evoke Studio Web Design Process:
1. Discovery Call — 30 minutes, we learn about your business, clients, and goals. You share any existing brand materials. We confirm scope and fit. Scheduled within 3 business days of your enquiry.
2. Proposal & Contract — We send a written proposal with scope, timeline, and fixed price within 3 business days of the discovery call. No surprises after you sign.
3. Design & Build — We design and build your site in Next.js. You review 2 rounds of design before development begins. Total: 4–6 weeks.
4. Launch & Handover — We handle the technical launch. You get full access, a walkthrough, and a 30-day support window. Done.
That's 4 steps, each with a specific timeframe, a clear client action, and plain language. The services page guide shows how this process section fits into the broader service page structure.
Want to see exactly how a web project works with Evoke Studio?
Evoke Studio builds service business websites in 4–6 weeks. Transparent process, fixed pricing, from $3,500.
Yes, but tailor it. If you offer both web design and brand identity, the process for each differs meaningfully. A brand identity process emphasises research and concept exploration; a web design process emphasises design rounds and technical delivery. Generic 'here is how we work' copy on every service page is better than nothing, but service-specific process descriptions convert significantly better because they answer the specific questions a visitor to that service page has in mind.
All service businesses have variation by project. Present the standard process — what happens in the majority of cases — and note exceptions clearly: 'For more complex projects, we add a dedicated research phase before design begins.' This is more useful to a visitor than 'every project is different,' which tells them nothing. Show the typical process; address exceptions in the FAQ or the discovery call.
Use plain language and real timeframes. 'We start with a 30-minute call' is warmer than 'Phase 1: Initial Requirements Gathering Session (30 minutes, remote).' Include the human element: what you're trying to find out in that call, what the client will experience. The goal is for a prospective client to read your process section and feel like they already know what working with you will be like — before they've even spoken to you.
Only if you present it as a rigid checklist that clients feel they can negotiate down. Present the process as what produces the best result — 'we do it this way because it produces the best outcomes, not because it's convenient for us' — rather than as a bureaucratic requirement. Clients who understand why each step exists are less likely to try to remove steps to reduce cost, and more likely to respect the process as integral to the outcome.
Process before pricing on a service page is the standard sequence: understand what the service is, understand how it's delivered, understand what it costs. This mimics a good sales conversation: value is established before price is revealed. Showing price before process can make the price feel unsupported — the visitor sees a number without yet understanding what it buys, which makes it easier to dismiss.