Case study: website, CRM and Telegram bot for a workshop that repairs Swiss watches
A workshop that repairs Swiss watches ran on a weak WordPress site and more than 12 years of client records in Excel. We built a new premium website, a CRM for the watchmakers, a Telegram bot that serves clients, and analytics in the CRM that made it possible to manage the business properly.
The client and the starting point
We don't name the client. The business, the work and the results are real.
The workshop repairs Swiss watches, a premium service. Its tools did not match it: the website was a weak WordPress site, and the whole client base, more than 12 years of it, lived in Excel spreadsheets.
A spreadsheet keeps records, but it does not run the work. It does not show a watchmaker which orders are waiting, it cannot answer a client who asks about their watch, and it gives the owner no clear picture of the business.
The goal was to move the workshop onto its own system: one place for clients and repairs, a bot for the routine conversations, and a website that looks like the service it sells.
What we built
A premium website
A new website on a modern stack with a strong design. It replaced the old WordPress site and presents the workshop at the level of the watches it services.
Our own CRM for the watchmakers
A CRM built around the workshop's work with clients: clients, watches and repair orders in one place instead of spreadsheets.
A Telegram bot for clients
The bot talks to clients, names repair prices and reports the status of an order. If a client is in another city or region, the bot calls a courier on its own.
Before-and-after photos and automatic posts
The bot saves photos of each repair before and after. When a repair is finished, it publishes a post to social media on its own, built from the order data and those photos.
Analytics in the CRM
Analytics built into the CRM that made it possible to manage the business properly.
SEO
Search optimization for the new website, so people looking for the service can find the workshop.
How it works now
Step by step
- CustomerA client writes to the workshop's Telegram bot.
- SystemThe bot answers, names the price of the repair and, if the client is in another city or region, calls a courier.
- TeamA watchmaker repairs the watch and keeps the order up to date in the CRM.
- SystemThe bot saves before-and-after photos and tells the client the order status when they ask.
- SystemWhen the repair is done, a post built from the order data and photos goes out to social media.
- TeamThe owner follows the business in the CRM analytics.
The system does
- Answers client questions in Telegram
- Names repair prices
- Reports order status
- Calls a courier for clients in other cities and regions
- Stores before-and-after photos of each repair
- Publishes a post to social media after a repair
- Collects the analytics in the CRM
People do
- Repair the watches: the craft stays with the watchmakers
- Keep orders up to date in the CRM
- Manage the business using the CRM analytics
Before and after
| Area | Before | After |
|---|---|---|
| Client records | Excel spreadsheets, more than 12 years of them | The workshop's own CRM |
| Website | A weak WordPress site | A new premium website on a modern stack, with SEO |
| Price and status questions | No bot | Answered by the Telegram bot |
| Clients in other cities | No automatic courier booking | The bot calls a courier itself |
| Social media after a repair | No automatic posts | A post from the order data and photos, published automatically |
| Picture of the business | Data spread across spreadsheets | Analytics in the CRM |
Result
The workshop runs on its own system now. Client work, order statuses, repair photos and analytics are in one place instead of spreadsheets. Routine client conversations about price, status and couriers go through the bot, and a finished repair becomes a social post without anyone writing it. The analytics in the CRM made it possible to manage the business properly.
Results in numbers
- Around 300 a month, roughly 6 in 10
- A few hours → under a minute
- Around 30 a month
- About twice as much within 6 months of launch
Project snapshot
- Scope
- Website, CRM, Telegram bot, analytics, SEO
- Channels
- Website, Telegram, social media
- Client size
- 3 watchmakers; around 150 repairs a month
- Timeline
- About 4 months for the website, CRM and bot
- Period
- Launched in 2024; support and SEO ongoing
- Team
- Two senior developers: website and CRM, bot and integrations
- Stack
- Next.js, React, PostgreSQL, Telegram Bot API, n8n
Next step
Describe the situation in a few lines. One of the founders replies and says whether we can help and what the first step would be.
Discuss your project