Ordering flow and operational logic
Demolice Recyklace — from a presentation website to an ordering and operational tool
A new website for a regional service company, where we needed to combine a more credible presentation with a real container ordering flow.
Project snapshot
- Category
- Ordering flow and operational logic
- Role
- Information architecture, UX of the container ordering flow, full-stack implementation of the website, ordering system, admin, and CMS layer.
- Context
- Demolice Recyklace / MINUTY a.s. is a regional company for demolition, recycling of construction materials, containers, and related services in Prague and Central Bohemia.
Starting point
What needed to change
The original website had a clear brand but a weak conversion path. Key information was in PDFs, online container ordering was missing, and customers had to look up or verify many conditions by phone.
Decisions
How the solution was shaped
The project was driven by a few decisions that made the delivery commercially useful, not just presentable.
- We turned containers into a standalone conversion pillar. Instead of hiding the service in general navigation, it received its own funnel with clear entry logic by order type.
- We converted pricing and rules from PDF to HTML. We extracted important business information from unclear PDFs into a structure that's easy to read, compare, and find without unnecessary phone calls.
- We designed the ordering as a real MVP for the company's operations. We didn't promise automatic scheduling. The flow intentionally ends with manual confirmation by an operator to match the actual operational reality.
- Alongside the presentation layer, an internal operational foundation was created. Orders flow into an admin panel and notifications, so the website functions not just as a marketing facade but also as an entry point into the internal process.
Constraints
- We needed to preserve the existing brand while rebuilding the website to work better commercially.
- The public ordering had to match the actual service area and operational conditions, not just an ideal marketing scenario.
- The project required a balance between simplicity for the customer and what the company can actually handle internally.
Delivered
- Complete new company website with new information architecture.
- MVP online container ordering for a selected service type and service area.
- Conversion of pricing, rules, and key information from PDF to HTML.
- Admin, CMS layer, email notifications, and funnel measurement foundation.
What changed
- The website no longer serves only as a presentation surface but guides visitors to a specific order.
- Key service conditions are findable directly on the website instead of in attached documents.
- Customers can get a clearer picture of the service before they need to call an operator.
- The internal team has materials and inputs from the ordering flow in a usable admin panel.
What we can demonstrate
We only publicly describe what we can demonstrate through architecture, flow, and implementation.
- Sitemap, product decisions, and structure of the container funnel.
- Implementation of the admin, form flow, notifications, and funnel measurement.
- Technical implementation including builds, linting, type checking, and E2E testing of critical scenarios.
- Screenshots of admin, audit log, and selected operational artefacts.
Working on a similar service website or flow?
Send your project context and I'll propose next steps.