A school's shop online in two minutes, no developer needed

Behind some forty school shops there is a lot of daily work. Portals to open, prices to update, orders to follow, customers to notify, documents to check.

Studio Kyron is the internal app where Kyron's team does all of it. Each area has an agent with its own name. You work by writing, as in a chat, and next to the chat there is always the real list: portals, orders, customers or products.

Before: an hour or two per school

At the start, opening a school's portal was a developer's job. Someone had to prepare the configuration, fix the same three mistakes every time, load it into two environments, ship the code, wait for two site rebuilds and run the final checks.

It took one to two hours per school, and it always needed a technical person. With dozens of schools on the way, it was the bottleneck of the whole project.

Livia interviews the salesperson

Today the salesperson opens Portals and types: let's create a new portal. Livia, the portals agent, takes it from there.

She asks the right questions, one at a time: which school, which products, which kits, which discounts, where to deliver. Nobody has to type product codes. She shows the catalogue inside the chat and the salesperson ticks what they need. Kits are put together the same way, and she asks for the school's logo.

Before saving, Livia checks everything against the real catalogue and fixes the usual mistakes herself. A mistyped product code never reaches the live site.

Agreed prices are checked by a person, on purpose. Then one click on Publish. In about two minutes the school's shop is live, and the team gets an email confirming it.

Eight agents, each with a job

• Livia, Portals: opens and edits the school shops.
• Elsa, Tax relief: reads the documents for reduced 4% VAT, says what's missing and suggests whether to approve or reject. A person always decides, and the documents are not stored.
• Ada, Statistics: numbers for the site, the shop and the ad campaigns. Read-only, and she answers with tables and charts.
• Teo, Products: catalogue, stock and prices. Every price change goes through a plan he shows first, and only applies when you say so.
• Nico, Orders: filters orders, updates their status and writes to customers starting from delivery notes.
• Bea, Customers: customer records, order history, internal notes and saved groups.
• Ivo, Requests: collects what the team needs, asks a couple of questions, checks it isn't a duplicate and opens the ticket for us.
• Vera, Preview: looks at the website with you. Select a piece of a page and she writes the review note.

The chat shows tools, not just text

The agents don't only reply in words. When it helps, real tools appear in the chat: the catalogue to tick, the kit builder, the logo upload, a proposal card, a chart.

The list next to the chat moves with the conversation too. Type "the portals in Bari" and Livia filters the list for you. If you'd rather search yourself, the search box is right there.

Every write asks first

Reading is free. Writing isn't. A price change, an email to a hundred customers, a new ticket: the agent first shows what it's about to do, then waits for your yes.

Customer emails go out in batches, after a preview and a test send. And the same message never reaches the same person twice.

A summary in the inbox every morning

Nobody has to remember to open Studio to know how things are going. Every day an email arrives with the site's visits and enquiries, plus a price check across all portals that flags anything out of place.

What changed

Opening a school went from one or two hours of technical work to about two minutes, done by the people who sell. The team asks the agents for things instead of waiting for us.

The rest of the daily work, from orders and customers to reduced-VAT paperwork, lives in the same place with the same rule: the agent prepares, a person decides.