Rudolf Systems — geometric markrudolf.systems

Less manual work. The same team. More done.

Fast replies to client requests

Client requests are one of the slowest information flows. If every reply starts with searching prices, stock, old proposals, and chats — that is manual work worth reviewing.

  1. Client request
  2. PricesStockSuppliersRules
  3. Calculation
  4. CHECKREADY
  5. Commercial proposal
  6. Reply to client

Before

  • 30 min
  • 1 hour
  • half a day

After

  • 1–2 minutes
  • human review
  • reply to client

What you order

What you can order

If every client reply is assembled from prices, stock, old proposals, and chats — that is manual work. Each request from email, forms, and chats lands in one record. The system prepares a draft calculation, proposal, or reply — the manager does not hunt prices, stock, or suppliers by hand. CHECK flags gaps, READY means ready for review. Every request becomes data you can analyze later.

First — a review of your process. If the route makes sense, we build it for your situation.

Write for a free review

If you recognise this — we should talk

  • every reply starts with searching prices, stock, old proposals, or chats
  • clients wait for a reply
  • small requests are postponed
  • proposals are built from zero or copied from old files
  • unclear who replied to the client and when

Who this is for and what they get

  • Business owner

    • request queue and statuses are visible
    • can see where replies get lost
    • prices, lists, and suppliers sit in the route
    • does not manage every request by hand

  • Sales

    • proposals are not built from zero
    • CHECK or READY is visible
    • manager edits a draft, not an old template
    • client reply goes out after review

  • Request manager

    • does not hunt every price in different places
    • does not keep status in their head
    • sees what is missing for a reply
    • small requests are not delayed only because of manual routine

  • Supply / operations

    • price lists, stock, and suppliers can be part of the route
    • missing data is visible
    • disputed cases go to CHECK

What is done by hand today

  • request in email, details in messenger
  • price in one file, stock in another
  • old proposal copied by hand
  • manager clarifies in chats
  • small requests are postponed

What the manager stops doing for every request

  • the request lands in one route
  • the system gathers data for calculation
  • CHECK shows what is missing
  • READY means the draft can be reviewed
  • the manager does not start from zero
  • every request becomes a record with status — not lost in chats

What the business gains

  • proposals are not assembled by hand from zero
  • small requests do not stall only because of manual routine
  • visible gaps in price, stock, or rules
  • managers work with clients, not file copying
  • the owner sees queue, statuses, and bottlenecks — request data stays for later review

What the result looks like

Instead of spending 30 minutes gathering the pieces — a draft already filled in, a flag where something is missing, and a clear next step. The manager edits. The client gets a reply the same day. Every request stays in the system — so you can later see repeated delays and data gaps.

This is not a final CRM. Example result logic: client request → what is missing → CHECK / READY → draft proposal → owner.

Anonymised mockup — not a real request.

New request · manager
new request
REQ-2026-0881
client asks
3 lines, delivery Jun 12
missing
SKU line 2
draft proposal
CHECKto edit
status
CHECKawaiting review

What it looks like inside

Anonymised technical view of the route. The screenshot shows process structure, not client access, rules, formulas, prompts, or internal logic.

Anonymised working request-and-proposal route in n8n

After launch

  • Process map — route and review points are visible
  • Backup and documentation for the team
  • Handover to another specialist is possible
  • Fields, price lists, and rules can change after review
  • The route is not a black box
CHECK

CHECK is not a system failure

CHECK means the system is missing data, a rule, or a human decision. The system does not invent the answer. It stops and shows what needs review. For requests, this may be a missing price, material, supplier, rule, or owner decision.

Managers stay in control

The system prepares the calculation or proposal draft. The manager does not assemble the reply piece by piece — they review, decide, and confirm.

  • CHECKthe system does not invent the answer — only what is described
  • CHECKa person reviews before action; auto-send to the client is off
  • CHECKCHECK and READY are different statuses

What we do not promise

We do not sell a magic button. The system does not invent the answer — CHECK shows what needs review. A person decides.

  • We do not replace the manager or CRM without review
  • We do not promise 100% error-free output
  • We do not invent prices or rules — CHECK shows what is missing
  • We do not automate chaos — we review the process first
  • We do not send a client reply without review
  • We do not promise auto-sales — the system prepares, a person decides

Tell us what happens between a client asking and the manager replying

Describe what the manager does before sending one reply. That is enough for us to see where the time goes.

First step — process review.

Write for a free review

You can also find Denys Rudolf / Rudolf Systems on LinkedIn, Facebook, or X/Twitter.