From one café to three products: building Voku with agents

Where it started

It started with a café. Felipe Schneeberger bought one and needed a system to run it: sales, the kitchen, inventory, the cash register.

There was no shortage of options: apps like Fudo and Toteat already do this in Chile. So the question wasn't "how do we get a point of sale?". It was this: can agents build something better than what's on the market, and cover everything a business needs to run?

One business, three products

Running a business is more than selling. Once the point of sale existed, two more needs showed up, and each one became its own product:

• Voku ("Todo tu negocio, una sola plataforma."): point of sale and management in the browser. Sales, kitchen screens, tables, inventory, recipes, cash and reports, with Uber Eats and PedidosYa orders going straight to the kitchen.
• Voku Team: people management. Attendance and shifts, and a portal where workers find their documents and sign their contracts.
• Voku DTE: the connection with the SII, Chile's tax authority. It issues electronic receipts and invoices, signs them and sends them.

The brand, the three products and their landing pages were all built with agents. Voku is live. Voku Team and Voku DTE are going through their certifications with the Dirección del Trabajo and the SII, and the log at the end of this entry will say when each one is done.

The research came first

Each product sits on top of rules that are easy to get wrong. The agents researched the laws behind attendance records and electronic signatures, and the SII's technical manuals and schemas.

Attendance

In Chile, an electronic attendance system can't simply record times. In April 2024 the Dirección del Trabajo set the requirements in Resolución Exenta N°38:

• The system has to be certified by an independent company (not the developer, the seller or the employer) and authorized by the Dirección del Trabajo. The DT does not certify systems itself.
• Every clock-in produces a receipt the worker can access, and the employer keeps daily reports.
• Records must be protected against changes after the fact, and kept available for up to five years.
• Labor inspectors get their own inspection portal with access to the data.
• Workers are alerted when they forget to clock in or out, and employers about excessive hours, rest days and the right to disconnect.

Voku Team is going through that certification now.

Electronic signatures

To sign contracts inside Voku Team, the agents had to check what makes an electronic signature valid. Under Ley 19.799, a simple electronic signature is enough for most labor documents. An advanced signature is only required where the law asks for it, such as public instruments. The Dirección del Trabajo has accepted employment contracts signed this way since 2008, as long as they don't get in the way of inspections.

The SII

Voku DTE talks directly to the SII, and the SII is precise about how:

• Every document is an XML file that must match the SII's schemas, signed with XMLDSIG, with strict rules on algorithms and character encoding.
• Each document carries an electronic stamp (the TED), built from the CAF: the file in which the SII authorizes a range of folios for each company and document type. On paper, the stamp becomes a PDF417 barcode.
• Connecting takes a digital certificate: request a seed, sign it, receive a token. Invoices go through SOAP services; receipts use a newer REST API and have to reach the SII within one hour of being issued.
• Before issuing for real, there is a certification process in six stages: a test set, a simulation, information exchange, print samples, a declaration of compliance and, finally, registration as an electronic issuer.

Voku DTE is going through that process now.

Multi-tenant from day one

None of the three products was built for one café. Every app is multi-tenant: many businesses share the same software, and none of them can ever see another's data. In this field, that goes beyond keeping data apart:

• Taxes. Each company has its own CAF files and folio ranges, and its documents are signed with the certificate of someone authorized for that company. A folio used twice, or used by the wrong company, is a tax problem, not a bug.
• Labor. Each employer has its own workers, shifts and rules, its own audit trail, and its own inspection access for the Dirección del Trabajo. The provider also has to report its client companies to the DT every month.
• People. Voku Team separates access by role (worker, employer, HR, administrator), with a read-only portal for labor inspectors.
• Businesses with more than one location. Voku is priced per branch, for businesses with several locations.

Technically, the isolation is per row: every record carries the unique ID of the company it belongs to.

How it was built

Voku has one developer. Felipe spent most of the time writing tasks in Linear, with the agents connected to it.

• Code: Claude Code, with several versions of Claude Sonnet and Claude Opus, and Claude Fable.
• Brand: Claude Design, for the whole brand (more on it below).
• Landing pages: Google Antigravity, for voku.cl and voku.team.
• Checking the work: agents whose job is to validate what the others build. Each app's repository has more than 3,000 unit tests, and about 150 end-to-end tests cover the flows that can't break.

The brand

Claude Design made Voku's whole brand. Its manual sums it up in one line: one parent brand, three products, a single symbol.

• One symbol, three colors. The symbol is identical in all three products, down to the same path. Only the fill changes: orange #FF6B35 for Voku, blue #1A56DB for Team, green #0B7A4B for DTE. The symbol carries the recognition; the color tells the products apart.
• A wordmark that ends in a dot. voku., team. and dte. are set in General Sans at weight 650 and converted to outlines, so they look the same everywhere, with or without the font. The dot is parametric: its size, height and distance from the text all come from the type size, and it is never placed by hand.
• "por voku." Team and DTE carry the line por voku. ("by voku.") in footers, splash screens and about pages, never on the logo itself. Its dot is always Voku orange.

Each product has its own kit:

• 18 SVG logos: symbol, wordmark, horizontal and vertical lockups, and app icon, in color, black, white and a version for dark backgrounds. Every one also comes as a PNG.
• Favicons and social cards of 1200 × 630.
• Design tokens: a color scale from 50 to 900, shared neutrals, semantic colors and a type scale, as CSS, JSON, Tailwind and JavaScript.

All of it is tied together by a brand manual in a single HTML file: the family, the symbol, the wordmark and the dot, lockups, monochrome and dark backgrounds, color, typography, and correct and incorrect uses.

Seven months in commits

We didn't keep a record of the tokens. What we know is that the model was almost always Opus, and that for the first three months we hit the weekly usage limit almost every week, with five projects running at the same time, all of them Voku.

The git history does keep a record: 1,902 commits across seven repositories between March and October 2026. 1,647 of them (87%) were co-authored by Claude.

What went wrong

Building wasn't the hard part. Validating was.

The agents could build, but they lacked context about the other methods in the code. Our first answer was unit tests, lots of them. They helped at the beginning, but as the code grew, many of them no longer tested what they were supposed to validate.

So we added end-to-end tests for the flows that are essential in each app, checked from start to finish. The unit tests are still there; the end-to-end tests guard the flows that can't break.