Solution engineering · Multi-location hospitality
Every manual process you have runs once per location.
At two sites it runs twice. At five, five times. I spent years running food operations and I now build the systems that take those jobs off your team. One process, thirty days, fixed price.
Or call 778 956 4251. No pitch deck — you leave with the three processes worth automating, whether we work together or not.
The same six jobs, once per site, every week.
Solution engineering
What we take off your team
Not one product. Each engagement is one of these, built onto the systems you already run.
Reporting across sites
One number instead of four exports and a spreadsheet somebody rebuilds on Monday.
Invoices and cost
Captured, coded and matched to what you actually sold, without re-keying.
Guest messages and reviews
Answered at every location the same day, in your voice, escalated when it matters.
Menu and price changes
Pushed to every channel at every site at once, then checked that they landed.
Prep, checklists and compliance
Logged and chased without a manager standing over it, with a record when you need one.
Onboarding and training
Every new hire gets the same thing, not whatever the last manager remembered.
You do not have a software problem. You have the same job done five times.
Nobody puts it on a line item, so nobody costs it. But it is a salary, and it grows every time you open a door.
- Someone rebuilds the same spreadsheet every Monday.
- Someone consolidates four POS exports by hand to see one number.
- Someone re-keys invoices into the accounting system.
- Reviews go unanswered at three of your five sites.
- A price change takes a week to reach every channel at every location.
- New staff get trained from whatever the last manager remembered.
And you are in the gap
Single-venue tools assume one site and one owner doing everything. Enterprise systems are built for fifty locations and will not even publish a price. Between two and twenty there is very little, and there is no in-house developer to close it.
One expensive manual process. Thirty days. Fixed price.
Not a strategy engagement and not a pilot programme. At the end of the month the thing either runs without your staff touching it, or you do not pay the second half.
Week 1
Find it
I sit in your operation and pick the process worth taking. I know where to look because I have done these jobs.
Week 2
Build it
You see it working mid-week, not at the end. No black box, no long silence.
Week 3
Run it alongside
It runs next to your people in safe mode, doing nothing irreversible, while we compare its output to theirs.
Week 4
Hand it over
It goes live on your explicit go-ahead, documented — or we stop and you keep the documentation.
What I have built
All of it running in production, none of it a demo.
01
An agent that acts on live systems — and proves it did
Eight working tools against production. It updates a venue's published hours and changes what customers see on the public site. After every action it re-fetches the live page and confirms the change actually landed before it reports back.
Most tools tell you they did something. This one checks, and stays quiet when it cannot confirm.
02
A manual pipeline, replaced end to end
Taken off a no-code tool and rebuilt as a proper engine: rules, generation, review queue, approval, scheduling, publishing. Sixteen posts went from brief to live with a human approving, not producing.
59 unit tests and a written acceptance protocol, because a system nobody trusts gets switched off in week three.
03
A seven-agent team that holds roles
Project manager, developer, QA, backlog owner, sales — running on schedule in Slack, each with its own remit and its own limits.
They produce work items and reports, not conversation.
04
A decision system I will run on your problem
Six independent seats research a real business question in parallel, argue against each other, check every load-bearing number against primary sources, and produce one decision with the dissent recorded.
Last run: 61 claims checked, four strategies killed with evidence, in two days. Bring a decision you are stuck on and I will run it in front of you.
Who you are actually hiring
Yuriy Romanyuk
I spent years running food operations before I built any of this. I know which process is worth taking and which one is a broken process wearing a costume, because I have stood on both sides of that pass.
There is no account manager and no handoff. The person who sits in your operation in week one is the person who builds it in week two. Everything I ship holds to one rule I do not bend: after it acts, it re-reads the source of truth and reports what actually happened — or it stays quiet.
Vancouver, BC · yuriy@tasti.io
Who this fits
Operations big enough that a week of someone's time is real money, and small enough that nobody is going to build this in-house.
How I work
I will tell you when this is the wrong tool
Half of what looks automatable is a broken process wearing a costume. I would rather say so in week one than bill you for four.
Nothing irreversible without your word
Everything runs in safe mode by default and goes live only when you say so, channel by channel.
Your accounts, your data, your logins
I work with access you can revoke from your phone in ten seconds.
No black boxes
You get documentation of what runs, how it runs, and how to turn it off without me.
Pricing
Published, because you should not have to sit through a call to find out whether you can afford it.
Walk-through
Free
Ninety minutes in your operation. I come back with the three processes worth automating, what each one costs you now, and which I would take first. The list is yours either way.
Email meOne process
$5,000
CAD, fixed
Thirty days, start to handover. Half up front, half on handover — and no second half if it is not running.
Start hereOngoing
$3,500
CAD / month
Once something is live: monitoring, changes and the next process. Up to twenty hours a month. Cancel any month.
Talk about itQuestions
Who do you work with?+
Food businesses running two to twenty locations in BC — restaurant groups, café and bakery chains, catering operations, food manufacturers with a foodservice arm, hotel F&B. Big enough that a week of someone's time is real money, small enough that nobody is going to hire a developer for it.
What counts as a process?+
Anything a person on your team repeats. Consolidating sales across locations. Re-keying invoices. Chasing prep and temp logs. Answering reviews at every site. Pushing a price change to every channel. If someone rebuilds it every week, it qualifies.
Is this an AI product?+
It is whatever the process needs. Sometimes that means a model doing judgment work, often it is plumbing between systems you already pay for. I will tell you in week one if AI is the wrong tool — half of what looks automatable is a broken process wearing a costume.
What happens if it does not work?+
You pay half at the start and half on handover. If the thing is not running at the end of the month, there is no second half and you keep the documentation of everything I found.
Do you need access to our systems?+
Read access to the systems the process touches, granted by you and revocable from your phone in ten seconds. Nothing irreversible runs without your explicit go-ahead, channel by channel. Your accounts stay yours.
Do we have to replace our POS or software?+
No. I build on top of what you already run. Replacing a working system is the most expensive way to fix a process and it is almost never necessary.
Show me the job nobody wants to do.
Ninety minutes, no pitch. You walk away knowing which three processes are costing you the most and what it would take to remove them — whether we work together or not.
Email me