Skip to content
Zora

Work

Management software running in production, across sectors with nothing in common. The shared thread is not the trade: it is the calculation no off-the-shelf tool knew how to make.

Sectors covered

  • Coaching and training
  • Construction
  • HVAC
  • Short-term rental
  • Fitness clubs
  • Software publishing
  • The work is described without naming clients: the trade, the order of magnitude and what was built — never the identity.
  • Interface redrawn from the real mechanic, with neutral data. It is not a screenshot of the client’s system.
Coaching and training2026

Sales pipeline and commissions for a coaching provider

Off a no-code tool and onto a domain application that records commercial facts — appointments, sales, payments — then derives the pipeline, commissions and reporting from them.

Read the case study

Where it started

The entire sales operation lived in a no-code tool where one status field triggered a cascade of automations. The status had become the data: there was no way to know what had actually happened, nor to recompute a commission without replaying history by hand. Signed and collected were mixed into the same table.

What we built

We inverted the causality. The application records facts — an appointment has an outcome, a sale is signed, a payment arrives — and the pipeline stage is now only a projection of that history. Commissions are emitted by explicit rules at the moment of the fact, and become immutable. Signed and collected are finally two distinct notions.

What changed

A commission is justified by tracing back to the sale that produced it. Reporting recomputes from facts rather than from a current state, and fixing a historical error no longer breaks the running month.

Construction2026

A platform for a construction-industry network

Three spaces in a single product, web and mobile: a mapped member directory, a training platform, and management software for the building trade.

Read the case study

Where it started

Support happened by phone, email and in meetings — a proven method, but one that did not scale and left nothing behind between conversations. Each member ran their company on their own spreadsheets, disconnected from what they were being taught.

What we built

A platform where the network, the training and the management software reinforce each other: the mapped directory connects members, the training paths carry the method, and the management software puts it into practice — reference hourly rate, economic model and payroll are computed according to the method the network teaches, not a generic formula. All of it on web and mobile, over the same data.

What changed

The support method became a product. What used to be transmitted in meetings is now continuously available, and the calculations taught in training are exactly the ones members find in their software — something no off-the-shelf tool can reproduce, since it would first have to know the method.

HVAC2026

Jobs and field reports for an HVAC installer

A single tool to track jobs, schedule interventions and produce field reports, replacing a general-purpose task manager pushed well past its purpose.

Read the case study

Where it started

Tracking lived in a general-purpose task manager, topped up with emails, a shared calendar and an intervention tool. The same information was entered three times, and the link between a job, its interventions and its invoicing existed only in the owner’s head.

What we built

A model that takes the trade’s own vocabulary: the job is the parent entity, the intervention its child, and site work, breakdown call or refurbishment are merely job types. Reports are filled in the field — maintenance routines, readings, photos. External sources feed the application rather than the reverse: calendar, intervention software, down to equipment notifications arriving by email and parsed automatically.

What changed

One entry, at the moment the information exists. The owner sees the true state of his jobs without reconstructing it, and the assistant schedules, tracks equipment and invoices from the same screen.

Short-term rental2026

Real profitability for a short-term rental portfolio

A financial dashboard replacing an Excel workbook: automatic consolidation of booking revenue and accounting charges, then real margin computed by unit, by month and by channel.

Read the case study

Where it started

Profitability was computed in a multi-tab workbook, fed by hand from two sources: the booking platform and the accounting tool. Every month cost a full day of re-keying, and a miscategorised line skewed the analysis without anyone noticing.

What we built

Both sources now sync automatically into a single database. The cost-allocation rules — the workbook’s own, carried over one by one — became verifiable code. And lines the system cannot allocate with certainty are not guessed: they are surfaced for human arbitration before entering the calculations.

What changed

Profitability by unit, by channel and by month is continuously available instead of reconstructed. More importantly it is defensible: every amount traces back to the booking or the invoice that produced it.

Fitness clubs2026

Sales performance for a fitness club network

A sales-tracking portal whose progression mechanics reward consistency as much as raw performance — and stay fair whatever the size of the club.

Read the case study

Where it started

Performance was tracked club by club, in separate files, with a reward at month end. Between deadlines a salesperson had no short-term milestone to aim at, and a small club structurally could not compete with a large one.

What we built

A portal consolidating every club’s indicators, with individual targets and leaderboards. On top of it, a progression layer across several timescales: a weekly ranking, consistency streaks, career grades. Fairness is a design constraint rather than a setting — thresholds are relative to club headcount, so team size does not decide the ranking.

What changed

Recognition went from once a month to several times a week, and it stays reachable in a small club as much as in a large one. Sales tracking became something people open daily rather than a report they endure.

Software publishing2026

An AI support assistant for a software publisher

A support assistant grounded in the product documentation: it answers agents while citing the exact passage the answer came from, and stays silent rather than inventing.

Read the case study

Where it started

Agents searched a large documentation set by hand. Answer quality depended on how long the agent had been there, and the same customer could get two different answers depending on who picked up.

What we built

A documentation base chunked, vectorised and kept current automatically, queried through a conversational assistant. The design constraint was not model power but traceability: every answer carries its sources, and the assistant explicitly says it does not know rather than producing something plausible. Processing in Europe, with no data retention by the provider.

What changed

A brand-new agent answers from the same documentation as a veteran. And because the answer is cited, it is verifiable in one click: trust does not rest on the model, it rests on the source.

Let’s talk about your project

Describe what you are trying to build. We answer with an honest first read on feasibility and scope — even when the answer is that you do not need us.

Talk about your project