Загрузка…
A site with a catalog of crushed stone, sand, and asphalt, where a company employee edits the prices and every inquiry reaches both the CRM and email
0 to 1
Channels for taking inquiries, besides the phone
How we measured: before the project there was no website and inquiries were taken by voice and written down by hand; afterward, a lead from the site creates a deal in Bitrix24 and is duplicated as an email to the manager
The company hauls bulk cargo: crushed stone in various grades, sand, asphalt, soil. The work starts from an inquiry: a client needs a specific material, in a specific volume, delivered to a specific address, and they call to find out whether it's available and how much it costs.
The company had no website at all. That meant a client could only find it through word of mouth or a classified ad: in search, the company simply didn't exist. Everything that came in, came in by phone.
In search, the company simply didn't exist: a client could only find it through word of mouth.
The price list didn't live in a system either. The manager quoted prices for each grade from memory or checked a file on their computer. Bulk cargo is a market where prices move with the supplier and the season, and a file on one computer goes stale faster than it can be forwarded to colleagues.
An inquiry taken over the phone was written down by hand. From there it either made it into the records or got lost along the way, and that was only discovered when the client called back to ask when the truck would arrive.
The site was built from scratch, and it wasn't a five page business card site, it was a working tool for capturing leads. The structure was built around how a client actually searches: not 'about us' and 'our advantages,' but specific materials and hauling routes, because a person searches for 'crushed stone with delivery,' not for the name of a carrier they've never heard of.
The central part of the site is the catalog of hauled products. Materials, grades, specifications, and prices. The client sees exactly what the company hauls and how much it costs before ever picking up the phone, and calls already asking a concrete question about volume and timing.
The site's structure is built around how the client searches, not around how the company's departments are organized.
A lead from the site goes to two places at once: a deal is created in Bitrix24 and an email is sent to the manager. This is deliberate duplication, not redundancy.
A separate part of the work was the connection to 1C: the range of hauled products isn't entered into the site a second time, it's linked to the client's accounting system.
The price of crushed stone isn't fixed. It tracks the supplier's price, the season, the delivery distance. If only a developer can change it, and only on request, one of two things happens: either the company pays for every edit and waits, or the site's prices stop matching reality and a client calls quoting a figure that no longer exists.
The second outcome is worse than the first. A wrong price on the site isn't just an inaccuracy: the conversation starts with the manager explaining why the site says one thing while reality is another. Trust in the rest of the site's numbers doesn't recover after that.
A wrong price on the site is not just an inaccuracy: the conversation with the client starts with an explanation of why it says one thing while reality is another.
So we built an admin panel where a company employee changes prices themselves, adds and removes catalog listings, and edits descriptions and specifications. This is ordinary manager work, not a request to a contractor.
The same design means the catalog stays current. A new grade or a new material shows up, and it appears on the site the same day, not in the next paid batch of changes.
A lead from the site creates a deal in Bitrix24 and is sent as an email to the manager at the same time. The second channel exists for exactly one case: when the first is unavailable.
External systems are sometimes unavailable, and that's a normal state, not an outage. Bitrix24 has downtime and rate limits, and a lead sent in that moment, if there were only one channel, would simply vanish. The client, meanwhile, is confident they submitted it: they saw the success message.
The client saw the success message and is confident they submitted the inquiry. The second channel exists so that they turn out to be right.
The email closes this gap. Even if the deal wasn't created in the CRM on the first try, the manager still has the inquiry with the contact details and content, and the client gets called back.
The form itself is built to actually get filled in: it asks only for what's needed to process the inquiry, not everything that might theoretically be useful to know. Every extra field in a form is a share of people who won't submit it.
The company gained a channel it didn't have before. A client searching for crushed stone with delivery can now find this carrier, not just the ones who already had a website.
The conversation with the client got shorter: they see the price and availability of the material before calling, and call already with a real question, volume and address in hand.
An inquiry stopped being a handwritten note that might not make it through. It enters the sales pipeline, and its state is visible rather than held in the memory of whoever picked up the phone.
And the price list stopped being a file on one computer: a company employee changes prices on the site the moment they change.
The whole build took about a month, including the catalog, the admin panel, and both integrations.
The first conversation commits you to nothing: we will look at your situation and tell you whether you need a project like this at all.