Not services.[Systems].
Six modules that plug into one operating system. Start with the one that hurts most.
Not just a website.
Not just a chatbot.
Not just an automation.
One system that connects them.
Websites that capture
The front door of the system, not a brochure.
How it runs
What it is
Every form, button and chat link feeds the same pipeline. No inquiry depends on someone checking an inbox.
Who needs it
Businesses that get traffic, but inquiries still arrive by phone, DM and email in no particular order.
The problem it solves
A site that looks fine and captures nothing. No form, no clear next step, and a phone number you can't even tap on mobile.
What we build
- Webflow or custom-coded sites
- Multi-step inquiry and quote forms
- Prefilled WhatsApp and Viber links
- 301 migration maps off old sites
- Structured data, meta and share cards
- Forms that never fake a “sent”
Seen in
Status · Oct 2026
Lead pipeline & CRM
Every inquiry in one place, with a status.
How it runs
What it is
One list of every lead: source, details, where it stands. Usually a Google Sheet you already know, or the CRM you already pay for.
Who needs it
Teams that lose track of who asked what, and when.
The problem it solves
Inquiries spread across DMs, inboxes and notebooks. Nobody knows which ones got a reply, so some never do.
What we build
- Google Sheets or CRM pipelines
- Statuses and owner-only columns
- Rows coloured by status
- Reference numbers on every request
- Source and campaign tracking
- Duplicate and spam protection
Seen in
Status · Oct 2026
Automations
The repetitive work runs on its own.
How it runs
What it is
Notifications, confirmations, reminders and follow-ups that fire from the pipeline. The same way, every time, whether anyone remembers or not.
Who needs it
Owners who spend evenings copying, forwarding and reminding.
The problem it solves
Every confirmation, reminder and follow-up waits for a person to remember it. On a busy day, nobody does.
What we build
- n8n and Google Apps Script workflows
- Owner emails with one-tap call and reply
- Customer confirmations
- Reminders before and after the visit
- Daily and weekly reports
- Logged failures, so a failed email never loses a lead
Seen in
Status · Oct 2026
AI agents
AI that reads, sorts and drafts. People keep the relationship.
How it runs
What it is
Agents that read messages, work out what the person wants and log the lead. When a person is needed, they hand over. They never pretend to be you.
Who needs it
Businesses that answer the same ten questions every day.
The problem it solves
Replies depend on who is at the desk and how busy the day is. Slow answers lose leads, and the owner ends up reading every message twice.
What we build
- Inquiry sorting and qualification
- Reply drafts for your approval
- Lead follow-up agents
- Clear rules for when a person takes over
- Daily summaries of what came in
- Built on Claude or the OpenAI API
Seen in
Status · Oct 2026
Our lead agent reads replies to our outreach, answers, sends a sketch, proposes call times, logs every lead in a sheet and flags us when a person is needed.
We run it on our own business first. No client build uses AI yet.
Booking & orders
Requests arrive complete. You confirm instead of interrogate.
How it runs
What it is
Reservation, trial, pickup and order requests that reach you with dates, guests, time windows and every other detail already filled in.
Who needs it
Hospitality, fitness, food and local services.
The problem it solves
Every booking starts with a back-and-forth about dates, group size and times. Each round trip is a chance to lose the customer.
What we build
- Date, guest and time-window pickers
- Pickup and delivery scheduling
- Request numbers and confirmations
- Booking.com and messaging handoffs
- Dates that follow the guest across pages
- Clear wording: a request, not a confirmed booking
Seen in
Status · Oct 2026
Pricing & internal tools
The spreadsheet becomes an engine. Your team keeps control.
How it runs
What it is
Price and turnaround engines, settings sheets and internal views, built on the data you already keep.
Who needs it
Businesses with long price lists, turnaround times or custom quotes.
The problem it solves
Prices in a spreadsheet mean customers wait for a person. Rules in someone's head mean nobody else can run the day.
What we build
- Price and turnaround engines
- Owner-editable settings sheets
- Live statistics and driver views
- Pause switches and limits you control
- Specs for your existing software
One page.One form.One sheet.
And an automation that answers for you.
The smallest system that works on its own. All five client systems start from this spine: page, form, sheet, owner email.
Page
One page for one offer, written so the next step is obvious.
Form
A short form that asks the right questions and filters out spam.
Sheet
Every request lands as a row with status New. You move it along.
Automation
You get an email with one-tap call and reply. The customer gets a confirmation that it arrived.
Audit. Build. Run.
Three stages, each with an output you keep. Start with the first. Decide on the next once you have seen it.
Audit & blueprint
Finds where work leaks.
We map how a lead becomes a client, and mark every place work waits on a person. It starts with the free systems audit.
You get
- A map of how work moves today
- What to build first, what to automate, what stays human
- A proposal for a defined scope
Build
Closes the gaps.
Website, pipeline, automations and AI, built in the order the blueprint sets. Tested against the edge cases, not just the happy path.
You get
- A working, connected system
- QA on mobile and desktop
- Documentation for every automation
Run
Keeps the system alive.
We launch, train your team and hand over the documentation. Then we watch it, fix what breaks and connect the next module.
You get
- Launch and team training
- A handover written for the owner, not a developer
- Changes as the business grows
Our rule
Humans own relationships. The system owns process.
You own everything. Accounts, data and code live in your name. If we part ways, the system stays with you.
Get my free systems auditTools we build with.
Tools are the means, not the product. We pick them by the process and document every one.
01Build
02Automate
03AI
04Connect
Who owns the system?
You do. Accounts, data and code live in your name. If we part ways, the system stays with you.
Do you only build in Webflow?
No. Webflow is one option. The five client systems in our work are custom-coded sites with Google Apps Script and Google Sheets behind them, so the backend has no monthly fee. We pick the tool by the process, not the other way round.
Can it plug into the software we already use?
Usually, yes. We connect through REST APIs and webhooks where your software has them. Where it doesn't yet, we build the intake as a separate layer and write the spec for your developer. For Elegant, a dry cleaner with its own software, the switch from the sheet to their system is designed as a one-line change once their endpoint exists.
What does it cost?
It depends on scope, so we price it after the audit. The audit is free. You get a proposal for a defined scope before any work starts. We price the system, not the hours.
How long does it take?
It depends on scope. The audit shows what to build first. The proposal that follows sets the scope and the timeline before any work starts.
Do you work in Serbian?
Yes. We work in Serbian and English. Handover documents and setup guides for our clients are written in plain Serbian, for the owner rather than a developer.
What happens after launch?
We train your team and hand over the documentation: what runs, when and why. Then the Run stage keeps the system alive. We watch it, fix what breaks and connect the next module when you're ready.
Do I need to change the tools I use?
No. We start from what you already use: email, Google Sheets, WhatsApp, Viber, the software you already pay for. The system connects them. Our client pipelines so far live in a spreadsheet the owner already knows.