Free
EUR 0
Sign in and use it. Nothing is metered in the product today, and we will tell you before that changes.
The system a small agency runs on.
Clients, calendar, work and money. One shared context for the people doing the work.
Continue with GoogleNo card. About a minute.
Part one · The product today
What runs today.
Five stages of client work, from the first contact to the invoice. The interface previews below are illustrative.
1.0 Win
Keep a contact database that cleans itself.
Contact lists rot. Taoro dedupes on exact email automatically and queues the uncertain matches for a side by side merge screen.
- Fifty structured fields on every contact, plus tags, colored labels and segments.
- Thirty plus filter dimensions with live counts, so you see the size of a segment before you commit to it.
- Do not contact records include a reason: manual, unsubscribe, hard bounce or spam complaint.
- Describe who you want in a sentence and get real, enriched contacts added to your list.
Illustrative product preview
2.0 Book
Let clients book real time, on your domain.
A booking page that offers a time you are already busy for costs you a client. Taoro reads your Google Calendar for busy time before it offers anything.
- Buffers before and after, a minimum notice window, and a cap on how far ahead anyone can book.
- Daylight saving handled correctly, including split shifts across a single day.
- Run it on your own domain. Add it, we show you the DNS records, we verify it.
- Every booking guest becomes a contact in your database automatically.
Illustrative product preview
3.0 Run
Model the work, then let rules move it.
Agency work does not fit a to do list. A board here is a configurable data model with fifteen column types, formulas, and rollups that show a parent's live progress across its children.
- Table, board, timeline and calendar views over the same data.
- One click installs a complete creative production setup with nine workflow stages, a copy track, a client visible flag, legal approval, per role hours, and the automation pack that runs it.
- Send a client one link to a board view and choose column by column what they see.
- Files live on your Box or Google Drive, with automatic failover, full version history, and a trash you can recover from at three levels: the task, the file, and the individual version.
Illustrative product preview
4.0 Bill
Invoice, chase and reconcile without a second tool.
Most work tools stop at a time log and hand the rest to a spreadsheet. Taoro posts real double entry journal entries under every invoice.
- Accrual profit and loss and cash flow, read from the ledger the invoices wrote.
- Overdue invoices chase themselves. Set the cadence once, override it for a VIP client, pause it on a single invoice, with a pay by card link in every reminder.
- Your client pays that link by card through your own Stripe account. The money never touches ours.
Invoicing and receivables, with real double entry behind them. No accounts payable, no expenses, no balance sheet, no PDF yet, and bank statements come in as pasted CSV.
Illustrative product preview
5.0 Govern
Decide who can do what, and with whose keys.
Owner, admin and member is not a permission model for an agency with contractors and a client facing junior. Taoro ships twenty eight separate permissions across eight roles.
- Build your own role, without ever granting yourself something you do not already have.
- Bring your own accounts: Postmark, Google Calendar, Apollo, Apify, OpenAI, Stripe and Hubstaff. Each is stored encrypted and has a connection test.
- Every request rechecks your membership against the database, not just the token in your browser.
Illustrative product preview
Boundaries
Rules move work. They do not message people.
Automation here is a builder you author, and it runs on a schedule you can predict. A rule fires on a status change, on a new item, or on a button click. It can advance a status, roll a subitem's completion up to its parent, set a cell, archive an item, or link across boards. The queue drains every five minutes. A rule fires at most once per event, even if the queue retries it. A change caused by a rule can trigger at most three levels deep. Every run writes an internal execution row. There is no operator facing run history panel yet.
Notifications elsewhere do work: intake forms, booking confirmations and reminders, overdue invoice chasers, and lead updates each have their own delivery path.
Illustrative product preview
Automation ruleProduction board
Trigger
When status changes
ConditionsStatus is In review
Board is Campaign production
+ Add condition
ActionsSet status to Approved
Set cell Review date to Today
Link item across boards to Client work
+ Add action
Runs every five minutesSave rule
None of this is a surprise we are holding back.
- Your client can see the board. They cannot comment on it, they cannot approve on it, and they cannot attach a file to your intake form. Client comment is next; client upload after it.
- Rules fire on a status change, a new item and a button click. Not on a date, not on a field change, not on an assignment change.
- Invoicing and receivables, with real double entry behind them. No accounts payable, no expenses, no balance sheet, no invoice PDF. Issuing an invoice does not email it. The only outbound invoice email is the overdue reminder. Bank statements arrive as pasted CSV. There is no bank connection.
- Guests cannot cancel or reschedule a booking themselves. There are no paid bookings, no deposits, no group events, no recurring bookings, no SMS reminders, and Google Meet is the only video option. There is no round robin host assignment.
- Email and password signup is broken in production. Google login and magic link both work.
The rest is on one page: what ships today →
The join
Anything that acts on your business needs ground.
This is the argument for building it in this order, and it fits in one table. Software that acts on your behalf needs somewhere to stand: one database holding the work, a queue that drains on a schedule, execution that does not repeat itself on retry, a bound on how far one change can cascade, execution rows the product can expose to an operator, a permission model granular enough to scope something that is not a person, a cap on what it can spend, and a way to tell you what it did.
Four are built. Two are partial. The last two are not built.
| Precondition | State |
|---|---|
One database holding clients, calendar, work and money | BUILT |
A queue that drains on a schedule, with claim and retry | BUILT |
At most once execution, so a retry never repeats an action | BUILT |
A depth cap and an action budget, so a chain settles instead of looping | BUILT |
An operator visible record of what every run did Internal execution rows are written. The operator facing run history panel is not built yet. | HALF |
A permission model granular enough to scope something that is not a person The twenty eight permissions exist and you can see them above. The rules engine does not use them yet; it runs with full access. | HALF |
A cap on what it can spend on paid calls | NOT BUILT |
A way for it to tell a person what it did | NOT BUILT |
Part two
What comes next.
The product sections above describe today's capabilities and their limits. Next: our operating principles and the controls we intend to build. Taoro has no agent layer yet.
How we work
We test it in our own agency first.
Sekta is KSTUDIO's internal workshop for operating ideas. Taoro is the product we sell. We bring selected lessons across, then build and check them in Taoro.
Keep the context together. Define what done means. Give every action a boundary. These principles guide Taoro; the capability list tells you which parts you can use today.
Read the five operating principles →Next
We build the three missing controls first.
Everyone on this list is a person.
Taoro does not have an agent layer yet.
Before anything else, three things, in this order.
- 01Next
A spend cap, so a paid call is checked against a budget before it is made.
- 02Next
A scoped runtime principal, so the rules engine acts with a role instead of with full access.
- 03Next
A run history panel, so what the engine did is on screen rather than only in the database.
When we build the agent layer, it will be one more kind of action in the rules engine your team already authors, holding a role, spending a budget, leaving a run record. Not a chat window bolted on the side.
Further out than that is a way to write your standard operating procedures as things the system can run, with people owning the gates. That is a direction we hold, not a thing we are promising.
Illustrative product preview
Team4 members
Konstantins S.konstantins@kstudio.lvOwner
Alex R.alex@kstudio.lvAdmin
Marta O.marta@kstudio.lvMember
Dita K.dita@kstudio.lvMember
Price
Flat per organisation, with seats included.
Studio
EUR 89/ month
The entry point for a single operator or a team of two or three people, with included seats and per seat overage above them.
Invoiced directly
Practice
EUR 249/ month
For an agency running client work end to end: booking, boards, invoicing and receivables, and the permission model.
Invoiced directly
Firm
From EUR 599/ month
For larger teams running custom roles across several client facing groups.
Invoiced directly
One thing to know before you read those numbers. Nothing in the product gates by plan today. The tier you choose is the tier we invoice. There is no checkout inside Taoro yet; founding places are invoiced directly and we set the organisation up with you. The founding offer for the first organisations is on the price page.
Run today's work on ground that holds what comes next.
Taoro is live. It runs our own agency every day, and Google login takes about a minute. Founding places are invoiced directly.
That booking page runs on Taoro.