How the founder of BDEVY helped Shed Shed Sheds strengthen its enquiry handling and customer care during a period of substantial revenue growth.
| Client | Shed Shed Sheds |
| Industry | Garden buildings, timber and fencing |
| Work delivered | Missed-call alert system and customer care system |
| Reported monthly revenue | £90K to £210K |
| Revenue increase | 133.3% |
| Project period | [Add implementation date and comparison periods] |
| Currency | Pounds sterling (GBP) |
To complete before publishing: the project period: the baseline month and the comparison month. Garden buildings are strongly seasonal, so a reader will want to know whether this compares like with like.
The business behind the project
Shed Shed Sheds is a family-run business supplying made-to-measure timber garden products, including sheds, summerhouses and garden offices, alongside timber and fencing products.
For a business selling bespoke products, a customer enquiry can be the beginning of a detailed conversation. A buyer may need to discuss dimensions, design options or suitability before deciding what to order.
That makes customer communication an important part of the buying experience. The website can introduce the products, but the conversation helps the customer move towards a decision.
My work with Shed Shed Sheds focused on two parts of that experience: missed-call alerts and customer care.
The opportunity: support the journey from enquiry to customer
A missed call leaves an open question: was it an existing customer, a new sales enquiry or someone ready to discuss an order?
An alert gives the team an opportunity to respond. What happens next matters just as much. The customer still needs help, answers and a clear next step.
These were the two areas I addressed through this project:
- Missed-call alerts: bringing attention to unanswered calls.
- Customer care: supporting how the business handled customer enquiries and ongoing communication.
The aim was to help the business make more of its customer conversations.
To complete before publishing: the actual starting situation: how missed calls were discovered, how customer enquiries were handled before this work, and the specific problems the team asked you to solve. Without this the reader has no idea what changed.
What I built
1. A missed-call alert system
The purpose of this part of the project was straightforward: make an unanswered call visible so that the team had an opportunity to act on it.
There is an important distinction between knowing that a call was missed and successfully recovering the enquiry. An alert supports the first step. A useful follow-up conversation is what moves the opportunity forward.
For this reason, the alert system formed one part of the wider customer-handling approach.
To complete before publishing: the actual workflow: which phone system generated the event, where the alert arrived, what information it carried, who received it, and what happened next. Include automated texts only if they were genuinely implemented.
2. A customer care system
This addressed the customer communication side of the project. A business needs to handle the conversation that follows an enquiry as well as recognise that the enquiry happened.
For a bespoke product supplier, that conversation may involve understanding requirements, answering questions and helping the buyer decide on the next step.
To complete before publishing: the delivered system: which channels it covered, what staff could see or do, how enquiries were organised, and how follow-up was managed. Only features that were actually delivered.
How the two parts fit together
The project combined attention to incoming calls with attention to the customer experience.
The missed-call alert system addressed the moment when a call went unanswered. The customer care system addressed the broader work of helping customers.
The underlying principle is useful for other businesses too: identifying an enquiry and handling it well are connected responsibilities. Improving one creates more value when the other is also addressed.
The results: monthly revenue increased by 133.3%
Based on my account of the project, the systems helped support growth from £90,000 to £210,000 in monthly revenue.
| Measure | Reported result |
|---|---|
| Starting monthly revenue | £90,000 |
| Later monthly revenue | £210,000 |
| Difference per month | +£120,000 |
| Percentage increase | +133.3% |
| Revenue multiple | 2.33x |
The percentage increase is calculated as:
(£210,000 minus £90,000) divided by £90,000, times 100 = 133.3%
These figures describe the change in total monthly revenue. They do not, by themselves, establish how much of the increase came specifically from missed-call alerts or customer care.
My assessment is that the systems contributed to the growth by supporting the way the business handled enquiries and customers. A more precise attribution would require linking individual enquiries and follow-up activity to completed sales.
To complete before publishing: the measurement note: the baseline month or average; the comparison month or average; the source of the revenue figures; and whether both figures treat tax, refunds and cancellations the same way.
To complete before publishing: relevant context, including any changes in advertising, prices, staffing, product mix or seasonal demand during the comparison period. Garden buildings are strongly seasonal, and a reader will ask whether the comparison spans a quiet month and a peak month.
What this project demonstrates
Customer communication deserves attention alongside marketing
Generating interest is only one part of growing a business. The experience after someone calls or makes an enquiry also deserves deliberate design.
This project focused on that part of the journey: the connection between incoming interest and the business's response.
An alert needs an effective next step
A missed-call notification is useful because it creates an opportunity to act. Its practical value depends on what follows.
For businesses considering a similar system, useful questions include:
- Who receives the alert?
- Who is responsible for returning the call?
- How does the team know whether the customer was reached?
- What happens if the enquiry needs further follow-up?
The answers help turn a notification into a working process. If it is the wording rather than the workflow that is missing, the missed-call text-back generator writes the message, and the missed-call revenue calculator puts a figure on what unanswered calls are worth.
Measure the workflow as well as the revenue
Revenue is the headline result, but operational measurements help explain it.
For future evaluation, businesses can track missed calls, callbacks completed, time to first response, enquiries that become quotes, and quotes that become orders.
These are recommended measures for understanding a system's performance. They are not additional results claimed for this project.
What this means for your business
If your business receives sales enquiries by phone, it is worth examining what happens when a call goes unanswered, and what happens after the customer reconnects.
Start with a recent sample of enquiries. Check whether someone responded, whether the customer received the help they needed, and whether the outcome was recorded. The speed-to-lead scorecard walks through the same questions and scores the answers.
That review can reveal where a missed-call alert system, clearer customer care processes or better connected tools could help.
The Shed Shed Sheds project is an example of the work I now bring to BDEVY: building practical systems around the way businesses handle enquiries and customers.
Find the gaps in your enquiry handling
BDEVY helps businesses improve how they capture enquiries, manage customer information and organise follow-up.
If you want to understand where your current process needs attention, request a free business audit.
We can review how incoming enquiries reach your team and identify practical opportunities to improve the customer journey.
Results note: Revenue figures are reported by the project implementer and describe total business revenue. The contribution of the missed-call alert and customer care systems was not separately measured. [Replace with the client-confirmed source and comparison dates once available.]
case study missed call alerts customer care system enquiry handling