ROBERT JUCHNIEWICZ / ROTOTYPE

Everything starts
with information.

From an electrical pulse to everyday work.

We learned to transmit pulses, voices and data. Today, I help connect people and tools so information reaches someone who can act on it.

Talk about your workflow Follow a business workflow

Integrations · Information flows · Feedback loops

01 / A SHORT HISTORY OF THE SIGNAL
ENERGYCIRCUIT

First: harness the energy.

Electrical phenomena have always been around us. Over time, we learned to generate, conduct and control electric current.

The same story. Closer to your business.

02 / A DAY AT WORK

A report. Hours. An invoice.
It is all information.

Follow the same information from paper to a decision. See what changes when we connect the tools a team already uses.

01

Someone knows. Everyone else waits.

An employee hands over a report. The planner types in hours; the accountant receives invoices. Each person has part of the picture.

EmployeePlanner
Hands over a reportTypes in hours
AccountantReceives invoices
Hours spreadsheetAccounting software
MANUAL HANDOVER
···

Separate workflows

The process at a glance—
Source Paper / conversation
Hours in view—
Invoice value—
Needs review—
Working hoursEntered
Waiting for entry
Invoice workflowCHF
F-041—Received
F-042—Received
On the desk

3 work reports

2 invoices to register

Knowledge is spread across paper and people.

Illustrative scenario · sample data

First I understand the information flow. Then I choose the connections.

Conversations, logs, traces, metrics and CSV files help locate the bottleneck. Sometimes connecting what already works is enough.

Explore my work ↗

03 / PEOPLE · DATA · SYSTEMS

Start with
how the business works.

A team has routines, a budget and tools that already work. I start there and look for the point where a focused connection can help.

People & daily work

Conversations reveal knowledge, agreements and exceptions that no dashboard records. I look at how information is created, passed on and understood.

Digital traces

Logs, traces, metrics and CSV reports help reconstruct events and handovers. I compare them with everyday practice to investigate possible bottlenecks.

Tools & constraints

Existing software, interfaces, exports, permissions and recurring costs shape what is practical. Ongoing maintenance is part of that decision.

Depending on the starting point: metrics in OpenMetrics format, views in Grafana or an existing CSV export. The question we need to answer determines the choice.

TURN THAT UNDERSTANDING INTO A DECISION

Connect what exists

When individual tools work, I examine the handovers: what information is missing where? Which API or export could close that gap?

Automate a defined step

Once the workflow is understood, repetitive steps can be automated. Ownership, exceptions and feedback belong in the same design.

Build a focused addition

When a real gap remains, a website, portal or small custom module may fill it. Scope, operation and handover are considered together.

04 / FROM THE IMPLEMENTATION

The interface and
the workflow belong together.

Zentrali and the connected Aroma and Helvetia websites show my work so far. Here are my contribution, the connections and the publicly accessible interfaces.

01 / Web app · customer portal · operations

Zentrali

In use · public demo available
Zentrali website editor showing menu categories, draft status and a preview of the Verona demo website.
Actual capture of the public Verona demo · 16 October 2026

Make a change. Follow it through to the website.

Starting point
A restaurant needs one place to manage its menu, opening hours and announcements, and to keep track of enquiries.
My contribution
I developed the concept, customer and operator interfaces, implementation and deployment. I manage ongoing development and operation.
The workflow connection
A customer portal with drafts, preview and publishing, separate access for each venue and an operator area. Connected venues can also receive reservation enquiries and notifications.
View verification and context

The portal and connected websites are published. I checked the website editor and preview in the public demo; the restaurant publishing workflow is documented in the code and operating records.

Try it yourself: Verona is a fictional restaurant. Email and Telegram are simulated in the demo; no real messages are sent.

Open the public demo

02 / Websites · digital menus · integration

Aroma & Helvetia

Publicly accessible websites
Public Aroma website showing wood-fired pizza, its menu and the reservation enquiry link.Public Helvetia menu on a phone, with categories and prices in CHF.
Actual captures: Aroma website and mobile Helvetia menu · 16 October 2026

Information connects the owner and the guest.

Starting point
Guests need to find food, prices, opening hours and contact details on their phones. The owner needs a way to keep that information up to date.
My contribution
I designed and built the websites and digital menus, and connected them to Zentrali for content management.
The workflow connection
Two distinct websites with a shared technical foundation. The connected Aroma website also includes a reservation enquiry form.
View verification and context

The public websites and menus are accessible. I checked the Helvetia menu and language switch, and the available Aroma form. This review did not include a new test reservation or email delivery.

Aroma and Helvetia are connected implementations within the Zentrali ecosystem. The Aroma version linked here runs on its Zentrali subdomain.

View the Aroma website Open the Helvetia menu

05 / WORKING WITH AGENCIES

Understand the project
you already have.

I work with your existing software, data flows and team practices. Together we define the part I will take on: analysis, integration, automation or technical implementation.

Discuss working together

  1. Clarify the handovers

    Map the existing systems, people involved and unresolved connections together.

  2. Start small and make it visible

    Implement a bounded workflow and follow the information through to the result.

  3. Enable the next person

    Provide code, configuration and a clear handover for the team.

06 / FROM UNDERSTANDING TO OPERATION

Feedback is part of the solution.

  1. 01

    Listen

    Understand the goal, daily work, people and existing tools.

  2. 02

    Read the signals

    Bring available data and observations together. Record possible bottlenecks as hypotheses.

  3. 03

    Connect with a purpose

    Choose a manageable intervention and check technical feasibility.

  4. 04

    Close the loop

    Check the result, ownership, failure cases and feedback together.

  5. 05

    Check daily use

    Plan the handover, operation and agreed review of the effect.

07 / START WITH YOUR DAILY WORK

Show me where
things get stuck.

Describe one specific workflow: who does what, with which tools, and where information or feedback is missing. A few sentences are enough to start.

Describe your workflow by email

Direct contact

kontakt@rototype.ch

I will get back to you with questions and a suggestion for the first part we could investigate.