Client systems · Hilo · Signed · In delivery
An atelier counter that knows where every garment is
A custom operating system for a Triangle tailoring atelier, including migration of the existing Talus workflow into an owned system, staged so live orders are never stranded.
Client system. A custom operating system and workflow migration built by isonew for Martha Pineda at Unique Atelier. Signed and currently in delivery.
Service line: Custom Software Development
Context
What the operation looked like
A tailoring atelier running client orders, fittings, alterations and production stages through the Talus workflow plus manual tracking around it. Order state depended on staff knowing where a garment physically was.
Constraint
Garment work is sequential and physical. The system has to reflect where an item actually is in the atelier, and the migration cannot interrupt live orders that are mid-production with fitting dates already promised to clients.
Decisions
What was decided, and why
- 01
Migrate in stages with Talus live throughout, rather than a cutover date that would strand in-flight orders.
- 02
Model the garment, not the invoice, as the unit that moves through stages, because that is how the shop actually thinks.
- 03
Capture fitting appointments inside the order record so client communication and production state stop diverging.
- 04
Separate contracted scope from measurement: the operating benefits are the reason for the build, not a claim we make before they exist.
System built
What exists, module by module
Orders
One order record per client job, carrying scope, dates and status.
Measurements
Measurements captured against the client and reused across future orders.
Photos
Garment photos attached to the order so the reference travels with the work.
Signature
Client sign-off captured at the counter and stored with the order.
Production stages
Stage-by-stage state that mirrors the physical flow through the atelier.
Deposits and payments
Deposit taken at intake and balance tracked to collection.
Built with
Shipped
What it looks like in use
The delivered surface, live. Open it and check.
Evidence
No figures published yet
Release One Scope
The segment, the first release, and what was deliberately deferred.
The artifact handed over on this engagement. Client figures are replaced with representative ones, the structure is unchanged.
Contracted scope and current implementation are described above. Results are not measured yet and no outcome numbers are published for Hilo. Time savings, throughput and error reduction will only appear here once observed against a baseline.
Current state
Where it stands today
Signed and in delivery. Order and production modules in build, Talus migration staged, existing platform still live.
Next expansion
Client-facing fitting communication and a measured baseline comparison once the atelier runs a full production cycle on the system.
What this does not claim
Signed scope and current implementation are described here. Outcomes are not measured yet, so no time saving, throughput or error figure is published for Hilo.
Written and reviewed by
Ronan Pinho
Founder of isonew and of ChatSac, co-founder and CRO of ChurnDefense. Over ten years building and operating technology companies. Based in Apex, North Carolina. Works in English, Portuguese and Spanish.
Last reviewed 2026-08-14
Keep going
Other write-ups and the commercials
Same format, different relationship — plus what work like this costs.
One next step, and it is a paid one on purpose
The AI Opportunity Diagnostic is a fixed-scope engagement. You leave with a ranked plan you can act on with us or without us.