Reed Lifts
Positioning, website, Google proof and founder content. A closer look at the work behind the direct pipeline.
- Role
- Growth partner
- Scope
- Positioning, website, proof and content
- Evidence
- Founder-reported results in the published case study
- Role
- Growth partner
- Year
- 2026
- Status
- Live
- Result
- 8 jobs booked
From sub-contract work to a pipeline Reed owns.
Reed already did good work. The direct pipeline still lived on somebody else's phone, and every direct lead was an accident nobody could repeat.
What changed
I narrowed the position to platform lifts, built the mobile-first site in fourteen days, set up Google proof and published Harry's expertise every week.
Why it moved
The expertise was already there. We made it findable, credible and easy to contact.
“Sam's my man in the chair. Web, content, AI, the lot.”
- 8
- jobs bookedin the first two months
- 4
- jobs from one buyerafter one LinkedIn post
- 9
- Google reviewsholding a 5.0 rating
Read the evidence
The figures above come from the published case study. They describe its reporting period.
Eight jobs in the first two months
Reported by Reed’s founder. The case study records eight jobs in the first two months; these are jobs, rather than eight distinct buyers.
Source: published Reed Lifts case studyFour jobs from one buyer
The case study attributes four of the eight jobs to one decision maker following one LinkedIn post. It does not isolate the effect of a particular website element.
Source: published Reed Lifts case studyNine reviews at the documented point
The case study records nine Google reviews and a 5.0 rating. This historical figure is separate from the current live site capture.
Source: published Reed Lifts case studyMy role and scope
The published case study describes the positioning, website, Google proof and founder content. The interface walkthrough explains design choices rather than attributing individual enquiries to them.
Source: published Reed Lifts case studyThe decisions, on screen
A closer look at the website, contact path and content from the Reed case study.
Say what Reed does
- Problem
- A buyer needs to know whether Reed handles their lift and their area.
- Decision
- The headline names the services. The area served sits above it.
- Why it matters
- The opening screen answers the first practical question before asking someone to get in touch.
Make contact easy on a phone
- Call and WhatsApp are visible without searching through the site.
- The case study explains the decision: a contractor on site needs a quick way to reach Harry.
Use the founder’s experience
- The posts draw on Harry’s own work and relationships.
- These are examples of the content. They do not establish which post caused an individual enquiry.
The recorded walkthrough
14 seconds · silent recording · saved FloSumo version. This shows the case study presentation, rather than a new client result.
Read the visual transcript
0:00 · FloSumo homepage
The recording opens on the FloSumo homepage. The headline, navigation, call link and a LinkedIn performance image are visible.
0:03 · Reed overview
The page scrolls to the Reed Lifts case overview, with its website image, reported results and the published short quote from Harry.
0:08 · Open the case study
The recording opens the full Reed Lifts case study. Its title, service description and LinkedIn, WhatsApp and Google Business labels appear.
0:11 · Device views and starting point
Phone and desktop images of the Reed site appear together. The page scrolls to the original situation and the beginning of the results section.
What happens after the build
Your website should be something you can keep, edit and hand to someone else.
What you receive
The agreed website and content, with the code and assets. The scope is written down before the build starts.
What you own
Code, content, hosting and domain sit in your accounts. You can take the work to another developer.
How you edit it
We choose the stack around how you will use it. WordPress suits clients who want to edit pages themselves; bespoke Next.js builds suit different needs. We agree the editing workflow before building.
What comes next
The foundation is a project with an end date. Ongoing website improvements and commercial support are a separate monthly scope, agreed around the work you need.
Website approach at FloSumo → · Talk through a project →
A handover example you can inspect
A small example prepared from this website’s public Building page and design tokens, on 27 October 2026.
Open the sample files
- README.mdScope, file guide and build notes
- building-page.tsxActual public-page source
- design-tokens.tsActual design-token source
Show me what you have now.
Send me your website and the commercial problem behind it. I'll tell you what I would fix first.