Systems built around how your processes really run.

Simeonov Systems designs and builds custom systems for recurring business processes, covering the information, people, decisions and handoffs involved, from the first request to the final output.

Describe your process
See one process, on paper and in practice

On paper, and in practice

Take a piece of recurring work, such as a quote request, a supplier invoice or an inspection report.

Officially, it moves through four steps.

Illustrative example. Every process has its own version of this.

  1. Received

    Waiting for a missing detail

    It arrives by email without one detail that nobody can work without. Someone asks for it. The answer comes back two days later, in a different thread.

    Re: the details you asked for

    A new thread, separate from the original request.
  2. Checked

    Waiting for sign-off

    It needs approval from the one person who can give it. They are out until Thursday, so it waits in their inbox, behind everything else.

    Automatic reply: out of the office until Thursday

    The one person who can approve it.
  3. Approved

    Has it gone out?

    The approval comes back by phone. The spreadsheet still says ‘checking’. Whether it has gone out depends on who you ask.

    Status: checking

    The spreadsheet everyone is meant to keep up to date.
  4. Sent

    Until someone remembers

    What happens next is not written down anywhere. It happens when someone remembers, often after the customer has had to chase.

    Did anyone hear back on this?

    A message to the team, some time later.

None of the four steps is the slow part. The work waits between them: for a missing detail, a sign-off, an answer, someone to remember.

So the useful place to start is the whole process, from the first request to the final output.

What Simeonov Systems builds

Business process automation, built around how you work.

Simeonov Systems designs and builds tailored automation systems for real business processes. Sometimes that means automating one specific task; other times, connecting several steps, people or tools. The scope depends on what your business needs.

Depending on the process, a system could include forms that collect the right details first time, information passed automatically between tools, a shared record of where each piece of work stands, or documents produced from details already entered.

Where it can apply

Illustrative areas. Not a list of services or past projects.

  • Enquiries

    Every new enquiry recorded in one place, with a clear owner and a visible next step.

  • Orders

    An order followed from confirmation to delivery, its status visible to whoever needs it.

  • Internal requests

    Requests between people or departments raised, approved and tracked the same way every time.

  • Coordination

    Jobs passed between people, sites or shifts with what the next person needs already attached.

  • Recurring manual work

    Weekly and monthly routines, such as checks, summaries and reconciliations, done the same way each time.

  • Information between tools

    Details entered once and kept consistent across the tools you use, where those tools allow it.

Your process may not be on this list. That is fine: every system starts from how your business actually works, not from a list.

It works, because people keep it working.

Some signs turn up in very different businesses. Which of these happen in yours?

Tick the ones you recognise

Nothing you tick is sent or stored.

Automating a step makes it faster. A system changes how the whole process runs.

Illustrative example, continued from above. What a system takes on depends on the process.

The same example, two ways: who does what at each moment.

Who does what
Moment The system Your team
It arrives without a key detail. Asks for the missing detail as soon as it arrives.Nothing Picks it up once it’s complete.Spots the gap and asks for it by email.
It’s checked and needs sign-off. Runs the checks and sends it to whoever can sign off, or their cover.Runs the checks automatically. Automated Makes the decision.Waits for the one person who can sign it off.
Has it gone out? Shows the status in one place.Nothing Sees it at a glance.Asks around and checks the spreadsheet.
It’s sent. What happens next? Sets the follow-up when it’s sent.Nothing Talks to the customer.Follows up when someone remembers.

Automating one task is often useful in its own right. Where the process needs more, a connected system can also take on the hand-offs, coordination and follow-up around it, while your team keeps the decisions.

The process matters more than the industry.

Two businesses in the same sector can run the same work in very different ways, and very different businesses can share the same kind of problem. So each system starts from how your work actually runs, not from a template for your industry.

Where it is technically possible and suits the project, the automation works with the tools you already use.

Usually a good fit when

  • the work comes round again and again: daily, weekly or with every new request;
  • several people, teams or tools are involved;
  • keeping it on track takes manual effort, memory or a spreadsheet;
  • it matters enough to the business to be worth automating well.

When a ready-made tool may be enough

Sometimes an existing tool already does what you need, for example when:

  • the task is standard and the software you use already has a built-in way to automate it;
  • a widely used off-the-shelf product covers the whole need without being adapted to your process.

If so, that is often the quicker and simpler route. If not, smaller pieces of automation are welcome too: one well-built automation can be the right place to start.

Sounds like your process? Describe your process

Understanding the process

  1. Map how it runs todayWith the people who do the work, including the awkward cases.
  2. Find where it gets stuckThe manual effort, the waiting and the gaps in ownership.

Designing and building

  1. Redesign how it should runAgreed with you before anything is built.
  2. Build the systemAround the agreed design.
  3. Test it with real casesBefore anyone relies on it.

Testing often sends something back to the design. That’s expected.

Running and improving

  1. Put it into useAlongside the people who will use it every day.
  2. Refine itOnce real use shows what to change.

Start with one process.

Describe it as it really runs:

  • what happens today,
  • where it slows down,
  • and who is involved.

The real version, workarounds included, is more useful than the official one.

Describe your process

Submitting commits you to nothing.

What happens next

The person who reads your process is the person who designs and builds the system.

Simeonov Systems is founded and built by Bojidar Simeonov. If it looks like a good fit, he will get in touch to suggest a sensible next step, which is often a conversation.

Bojidar Simeonov Founder & Systems Builder