← All case studies
RapidLogic in-house project
TSL / Municipal services · Sales website (no-code)

A website that sells one system to three different audiences

This website was never meant to bring in search traffic, but to close sales conversations. After a call with a waste collection company we sent a message with a link, and the company could open an account straight from the page. We built it on the same platform as the rest of the system, so a visit to the website and work inside the panel are one session of the same user.

Tidly home page on a laptop: hero with a headline about commercial waste collection and two separate calls to action, one for customers and one for companies
46 h
Of work: copy, build, visuals, video
3
Lines of argument instead of one
1
Login for the website, marketplace and panel
0
Extra tools to maintain

The only window for someone who is not a customer yet

Tidly is an in-house RapidLogic project, a two-sided platform connecting homeowners with waste collection companies. We have already described the marketplace, the dispatcher panel, the driver app and the customer app. All four show the system from the inside, the way it looks to someone who already has an account. This case study covers the only window through which someone who is not a customer yet gets to look.

We started with the question of why this website should exist at all, and the answer turned out to differ from the obvious one. The website was not meant to attract search traffic, but to close sales conversations. After a call with a waste collection company we sent a message with materials and a link, and the page had a few minutes to explain what the system is and let the company open an account right away.

Every other decision followed from that, including the most important one: since the website is part of the sales process rather than a leaflet next to the product, it should run on the same platform as the product.

One page for three people who want different things

A two-sided platform carries a communication problem by design. On one side there is the homeowner who wants to stop calling companies. On the other, the waste collection company that wants to stop answering those calls. The same system solves both, except each side hears a completely different promise.

Conversations with operators surfaced one more thing that was invisible at the start. A company with a dozen trucks and a company with one truck are not the same customer. The first has a dispatcher, an office and a routing problem. The second is an owner-driver who writes invoices in the evening because he drives all day. An argument about automated territory planning means nothing to him, while a sentence about invoicing at night lands immediately.

A website without that split

  • One message trying to satisfy the homeowner and the company at once
  • A feature list instead of a promise, because features are shared while problems differ
  • The small company reads about fleet routing and does not see itself there
  • The website lives next to the system, on separate technology and separate data
  • The visitor has to open an account from scratch, with no trace of the visit

How Tidly does it

  • Traffic split in the home page header, with two calls to action
  • Three subpages, each with its own headline, promise and visual
  • The small company gets the invoicing argument, the large one gets jobs and office stress
  • The website is part of the system, on one technology and shared data
  • Logging in on the website carries the user onward together with the account

Split the traffic first, then hold three separate conversations

The home page does not try to sell anything. Its only job is to send the visitor the right way, which is why we put two calls to action side by side under the headline: search for a service for the homeowner, and a presentation for the company. The same split repeats in the navigation.

Selling begins only past that fork, separately in each of the three tracks.

Small company: no more invoices at night

With one or three trucks the owner is the driver, the dispatcher and the accounting department at the same time. The headline calls it software for drivers, and the promise addresses what this person does after hours: writing invoices in the evening and answering the phone on the road.

Tidly subpage for small waste collection companies: a headline about software for drivers and an isometric visual of a driver confirming a job from the cab

For an owner-driver what counts is simplicity and a system that runs without being managed.

Large company: less stress in the office, more jobs in the field

A company with a fleet has a completely different bottleneck. There is a dispatcher, the phone rings all day, and profitability depends on how the routes are arranged. The promise therefore is not about one person's comfort, but about replacing manual control with automation and about the number of jobs the fleet manages to complete.

The visuals follow the same distinction. The small company sees a cab and a single job, the large one sees an office, a fleet on the road and a treatment plant from above.

Tidly subpage for large waste collection companies: a headline about a system that works for you and an isometric visual with an office, a fleet and a treatment plant

The same product, a different promise: automation instead of manual control, and more jobs completed.

The problem shown in a photo, not described in words

Two sections on both company subpages do not list features, they put two situations next to each other. In the section about phone calls, the left side carries text about calls from six in the morning until eleven at night, on Sundays and holidays, and the right side carries two photographs: a driver with two phones at his ear, and the same driver calmly looking at one screen.

The second section does the same with paperwork. A pile of documents in the cab against an app where the address, the gate code and the required hose length sit next to the job. This is the same material we described in the dispatcher panel as the digital customer file, only phrased as a benefit rather than a feature.

The section about constant phone calls on the Tidly website: text about calls from 6:00 to 23:00 and two photographs of a driver before and after the system

The promise delivered as the difference between two photographs of the same person.

The section about lost addresses and phone numbers on the Tidly website: the digital customer file, logistics details and cooperation history

The digital customer file described by what it gives the driver, not by how it works.

Customer: one sentence instead of a feature list

The third track leads to the homeowner, and that conversation looks nothing like the other two. The owner of a septic tank cares neither about fleets nor about invoices, only about not having to think about the tank at all. The subpage headline therefore sounds exactly the way that problem sounds when someone says it out loud.

Tidly subpage for customers: a headline about forgetting the septic tank and an isometric visual with a house, a sensor and a relaxed owner

For a homeowner the promise is not a feature, it is having one less thing to think about.

A diagram that explains the scale in one picture

Whenever a sales conversation reached the question of what this actually is, words stopped being enough. Tidly is not one application but seven parts working together, and that is hard to tell in an email. Hence the diagram: on the left what the customer gets, on the right what the company gets, and in the middle two ways of taking orders, the company's own shop and the marketplace.

Diagram of the Tidly platform: customer panel, mobile app and sensor on the customer side, provider panel, driver app and reports on the company side, with the company shop and the marketplace in the middle

Seven parts of the platform in one picture, instead of a paragraph nobody reads to the end.

Video shot at the tank, not in a studio

The last element is a two-minute video that shows the problem where it happens: at the tank, in winter, on a driveway. Filming and editing took six hours and were done entirely in-house.

This is the same mechanism as the driver photographs. The viewer is meant to recognise a situation before hearing what the system does about it.

The section with the embedded video on the Tidly website: a two-minute film shot at a septic tank

Two minutes at a tank explain the platform better than a paragraph about automation.

A website grown into the system, not parked beside it

The usual arrangement in projects like this has the sales website built in one tool and the product in another. We chose the opposite and built the website on the same platform as the marketplace and the panels. There were four reasons.

That last point is the one you cannot see in a screenshot. When the website operates next to the system, a visit and a later sign-up are two unrelated events. When it is part of the system, they are one path, and the data left behind stays consistent.

What this website does not do

The website was built for one job, and everything that did not serve that job was postponed. With a sales website the first association goes to search optimisation, and here there deliberately is none.

Postponed

  • A blog and building traffic through content
  • Search optimisation beyond the technical basics
  • Split tests of page variants
  • Integrations with advertising systems

Why

  • We drove people to the website from phone calls, so traffic arrived by email rather than from search
  • Search optimisation makes sense once you know the product sells itself, and we did not know that yet
  • Split tests need traffic, and at that stage there was none
  • Analytics was ready, while the campaign was stopped by the decision to pause the project

How far this went. Analytics was prepared to measure traffic, while the website never received traffic at the intended scale. We started with local conversations, and before a larger campaign happened, the state-run Aquarius system appeared and the decision was made to pause Tidly, which we describe in the marketplace case study. So we have no sales results for this website.

Forty six hours to launch, around forty after it

The website was built alongside the platform, while the visuals and the video were separate work, outside the base estimate for the whole ecosystem. Below is how that part ran.

Around 24 h
Copy and building the website
Structure, the traffic split, three lines of argument and the texts. The copy came from three sources: market research, conversations with waste collection companies, and first-hand experience of owning a property with a septic tank.
16 h
Visuals and mockups
Two days on a full set of isometric illustrations and mockups. The demanding part was making them show situations from the field rather than generic pictures about technology.
6 h
Product video
A two-minute film shot at a tank and edited entirely in-house, with no crew and no studio.
Next 2 months
Refinement after launch
Around forty hours of fixes and improvements after the launch, based on what came up in conversations with companies. That part also falls outside the base scope of the project.
After 2-3 months
Stopped before the campaign
Local conversations instead of advertising at scale, followed by the decision to pause the project once the state-run Aquarius system appeared.

What this means for a company selling a system or a service

This website has no sales results, because the campaign never started. What it does have is a measured amount of work and a set of decisions that transfer to any project where one offer reaches several different audiences.

46 h
The whole website with its materials
Twenty four hours on copy and the build, sixteen on visuals, six on the video
3
Lines of argument
Small company, company with a fleet and homeowner, each with its own promise
1
Session across website, marketplace and panel
Logging in carries the user onward together with the account context
0
Extra tools to maintain
No second technology stack, no second content system and no second invoice

Why this matters beyond waste collection

Many companies need a website like this: every company that sells a system or a service and wants to close sales conversations. What sets this project apart is not the website itself, however, but the fact that it is grown into the system. For marketplaces and service companies that means the path from a first visit to an open account is one path, not two independent tools bolted together.

The second lesson is about segmentation. If you hear two different problems in your sales calls, you have two different customers, even when you sell them the same product. Splitting the website into three tracks cost a few hours of copywriting, while without it every one of those conversations would start by explaining why the offer concerns the person on the other end at all.

Today we would build this faster. The same scope delivered with AI-assisted engineering, which we show in the Fortress and Invoices case studies, takes around three times less time and money.

"

Technological consistency is serious leverage. Everything can be managed from one panel, the user logs in on the sales website and moves to their panel or to the marketplace, all the time within the context of their account. For us that means consistent data, not two separate worlds that somebody has to stitch together later.

Krzysztof Gromadzki, founder of RapidLogic
Krzysztof Gromadzki Founder of RapidLogic, creator of Tidly

Do you sell one product to several different audiences?

Splitting the traffic at the entrance, a separate promise for each audience and a website tightly connected to the system: in Tidly that scope closed in forty six hours. A free digital audit will show what such a website could look like for you and what could be connected to your system.

Book a free digital audit
See all case studies