A custom CMS for your catalogue and enquiries

When you need it

• Enquiries arrive by email and messenger, and some get lost.
• Quotes are put together by hand in Excel and Word, and prices are recalculated every time the exchange rate moves.
• Only one manager knows where a deal stands.
• Off-the-shelf CRMs cannot do what you need or take ages to configure.

What I have built

Control panels for six client websites: MIROTEC, Belmirotec, Mirozdanie, Belagra, Zavod PPS and Gruz+. Staff now handle things they used to call a developer for:

• enquiries with a client card: owner, next step, due date, deal value and outcome, source and UTM, Telegram notifications;
• an equipment and product catalogue: specifications, CSV and Excel import with a preview, edit history with restore;
• built-in statistics without third-party counters: sources, funnel, behaviour, monthly demand;
• a page builder, a price list with a calculator, an SEO check before publishing, redirects;
• staff roles, an action log, backups and automatic reports.

I have also built quote management inside a CRM and a client workspace for web projects.

You can see how it looks in the CMS demo, which runs on made-up data.

What else I can build

Calculations by your formulas, product finders, document generation, imports from Excel and supplier websites, translation, notifications, roles and access, API integrations. Describe the process step by step and I will tell you whether it can be automated and where to start.

How the work goes

1. I map the process: who does what, and where time and data get lost.
2. I describe the screens and rules. We agree on them before development.
3. I build a first working version on your real scenarios.
4. I refine it with your team’s feedback and hand over instructions.

Where to start and what it costs

We usually start with the one operation that eats the most time, such as building quotes or sorting enquiries. Once it works, we extend the system. The price depends on the number of screens, roles and integrations; I quote after mapping the process.

Which part of the process needs a system?

These are separate modules. The examples above come from different projects; not every client system has the whole set. If your existing system handles the task, configuring it may be enough.

For example, an enquiry workflow can be: receive the request → assign an owner → set a next action → record the outcome. We agree on the fields, roles and exceptions before building it. Try the roles and catalogue demo or describe one operation you want to automate.