POCCHITO TEAM
Pocchito is a companion you talk to: it sorts out the scheduling, the reminders and where to go, and the language model behind it is our own. It learns your preferences as you use it, so how those are handled is a workstream too.
WHO IT IS FOR
The person using it every day, the businesses it sends them to, and the developers connecting it to other services.
The person with the day to get through.
Workstreams serving them16
The places being suggested and booked.
Workstreams serving them2
The people connecting it to other services.
Workstreams serving them1
THE ROSTER
One workstream, one objective. What follows is not a snapshot of who is busy today — it is the set of workstreams this product needs.
5
The companion itself: say it however it came to mind, and have it done.
Conversation
Understand it the way someone would actually say it.
Users
Scheduling and reminders
Take over the arranging, and the remembering.
Users
Finding and booking
Find somewhere that fits, and get it booked.
Users Shops
Learning preferences
Learn what someone likes, and ask fewer questions each time.
Users
Notifications and voice
Speak up when it matters and stay quiet when it does not.
Users
2
The companion lives on the phone you already carry, and these workstreams own how it feels there.
iOS development
Own how it feels and ships on iPhone, and cut the steps before you can speak.
Users
Android development
Deliver the same experience on Android, without the handset getting in the way.
Users
2
Pocchito's language model is our own. Building it and judging it are deliberately separate workstreams.
LLM development
Build and improve the language model Pocchito runs on.
Users
LLM evaluation
Measure whether a changed model is actually better, against a fixed yardstick, kept apart from the people changing it.
Users
1
What the screens can do should be reachable from outside tools and AI agents too.
MCP / API
Let outside tools and AI agents work with Pocchito's features and data.
Developers
3
Building it is not enough. These carry someone from never having heard of it to using it.
SEO and content
Be findable, and say what it does before anyone has to ask.
Users
PR / SNS
Keep saying, outside, what this is actually for.
Users
Sales
Find the right prospects, make the case, and keep the thread alive. An agent researches and drafts; a person has the conversation.
Shops
2
Nobody gets stuck after they start, and what they tell us turns into a fix.
Help content
Let people solve it themselves instead of waiting for support.
Users
CS / QA
Answer what comes in, and turn it into a fault that cannot happen twice.
Users
1
The workstream that runs before anything is built: what was asked for, read against how it is used.
Feature requests
Gather what users ask for and what usage shows is missing, and decide what gets built next.
Users
3
It stays up, it stays protected, and the billing adds up.
Server watch / log analytics
Find errors and slowness first, so nobody meets them mid-task.
Security
Check on every change that what must be protected still is.
Users
Billing
Bill what was used, correctly and on time.
Users
THE LOOP
Every workstream turns the same way. A person sets the objective, an agent does the work, and the decision to ship comes back to a person.
See the eight stepsWhich errand gets taken off the person's hands. This part stays with people.
One session per workstream, started with the code conventions, the past decisions and the current numbers already in hand. A workstream that turns into a long piece of work gets a branch of its own.
Changes go out small, through review and an automated test suite, onto a staging environment — and a person makes the call to put them live.
Did it have to ask fewer questions? More conversation is not what we call a result.
ONE AT A TIME
The workstreams do not all run at once — one moves at a time. Our own model and the apps both fit because one conversation only ever holds one workstream.
Work on the model does not queue behind the iOS app. The model and how it feels in the hand move separately.
Code conventions and the quality bar are the same across the whole project. What stays separate is the mission and the context around it.
Decisions accumulate inside each workstream, so picking it up again does not start from zero.
When a workstream turns into a long piece of work, it moves to a branch of its own. The work is kept apart the same way the context is.
Many small changes rather than one large one — each inside a range we can roll back.
STILL OURS
More agents does not move the responsibility. That stays with people.
Learning someone's preferences means holding part of their life. What is kept and what is forgotten is decided by people.
We can do more than before. That is exactly why the decisions worth our time are the ones to decline.
Dates, estimates, quality. A company promises those, and a company is people.
Review and merge. A person presses the last button.
LET'S TALK
The way we run Pocchito is the way we run the work clients bring us. Tell us what you need moved first.
Talk to us