OS04

Where the work outruns the paperwork

Construction is physical, fast-moving work, and the administrative trail often struggles to keep up. Attendance may begin on a clipboard. Certificates arrive as photographs or attachments. Permits live in separate folders. Useful context passes through calls, messages and voice notes, then has to be pieced together when somebody needs a reliable record.

Teams care about process, but most processes have been designed around the needs of the record rather than the reality of the site.

I built OS04 through Stonecut to close that gap. OS04 brings everyday site activity into one operational system, helping field teams record what is happening with less friction and giving managers a clearer view of what needs attention. The ambition goes beyond replacing paper forms: fragmented activity should become useful, trustworthy site intelligence.

OS04 site view — attendance, compliance and context in one place

Starting with a moment that happens every day

The first product focus was deliberately practical—who is on site, whether they are cleared to be there and whether the right evidence exists afterwards.

Worker sign-in gave OS04 a narrow but important entry point into the operation. It connected attendance with location, identity and compliance rather than treating it as a timestamp in isolation. Dynamic forms could adapt the information collected for a particular site, while certificate records, permits and approval workflows helped managers understand whether requirements had actually been met.

Starting here gave me a clear product test. The worker experience had to be quick enough for the beginning of a shift, and the resulting record had to be useful to the person responsible later. If either side carried too much burden, the workflow would fall back to paper, messages and memory.

That balance—less effort at the point of capture and more value afterwards—became the organising principle for the wider product.

Designed for the conditions, not the presentation

Construction software is often demonstrated in a quiet room with a strong connection. The product has to earn trust somewhere very different.

Sites can have unreliable reception, workers arriving together and little tolerance for a flow that needs explanation. Location readings are imperfect. A person at the edge of a site boundary may be exactly where they should be, while a system interpreting the signal too rigidly could say otherwise. Compliance needs confidence, but it also needs judgement about the conditions in which evidence is created.

I shaped OS04’s field experience around those realities. Sign-ins can be retained when connectivity drops and completed when the device is back online. Location and photographic context strengthen the record without asking the worker to become an administrator. Clear, focused actions keep the mobile experience appropriate for the gate instead of squeezing an office dashboard onto a phone.

I did not treat these as edge cases to solve after the core product. They changed what “working” meant. A feature that succeeds in a demo and fails in a basement, a rural site or a steel-framed building is not a finished field feature.

Turning unstructured activity into useful information

OS04 uses AI inside existing work, where it can remove a real task. It is not presented as a separate destination that people have to remember to visit.

Certificates are a good example. The useful information may already exist, but it is trapped inside an image and still has to be read, entered and checked. OS04 can extract the relevant details and bring them into the compliance workflow, reducing repetitive administration while keeping the original evidence connected to the record.

Voice notes solve a different problem. Speaking is often the fastest way to capture context on site, but raw recordings are difficult to scan, share and act on. OS04 turns those notes into structured summaries so the ease of speaking can produce the clarity of written information.

Both features follow the same rule: use AI to remove the translation work between how people naturally capture information and how the business needs to use it. What matters is fewer loose ends, faster understanding and a more complete operational memory—not generation for its own sake.

OS04 dynamic forms — adapted per site, per requirement

One product across the field and the office

The person signing in and the person reviewing site activity have different needs, but they are participating in the same workflow.

OS04 therefore has a mobile experience for the field and a web workspace for management. Workers can complete immediate tasks without navigating the complexity an administrator needs. Managers can oversee people, sites, forms, certificates, permits and audit history without pushing that burden back onto the worker.

I kept those surfaces deliberately separate. Serving every role through the same interface would make the field experience heavier and the management experience shallower. Each surface can stay focused while the underlying record remains connected.

The product grew from attendance into a broader operational layer because the adjacent needs were already visible in the same journey. A missing certificate affects approval. A site requirement changes the form. A voice note adds context to an event. OS04 brings those relationships together so managers can follow the state of the work rather than assemble it from several systems.

OS04 reports — the operational picture, assembled

Separating the product from the company

I originally built and shipped the platform under the name Onsite. It described the first use case well, but became restrictive as the product expanded beyond presence and sign-in into compliance, records and operational intelligence.

Eight months into development, the product took on the Stonecut name. Moving away from Onsite reflected product-level learning: the name no longer held the wider system that had emerged from real workflows.

As Stonecut took shape as a broader home for my products, that solution exposed a different problem. The company and the construction platform had become indistinguishable, limiting both to the same category. The product needed a focused identity of its own, so it became OS04.

Those changes came from learning at two different levels. Onsite became too narrow for the product; Stonecut became too broad to serve as both product and company. Stonecut is the company. OS04 is the product.

The separation gives OS04 a clear construction focus while allowing Stonecut to build beyond construction without another structural change.

Building for continuity

I have designed and built OS04 as a solo founder and product engineer within Stonecut. That makes delivery discipline part of the product strategy. A broad operational product cannot depend on one person remembering every decision, and fast progress is not useful if each release weakens confidence in the last.

I organised development around explicit product behaviours, small bodies of work and automated verification. AI-assisted delivery increased the amount I could explore and ship, while clear acceptance criteria and recurring quality reviews kept judgement visible. That internal system stays behind the scenes. Its job is to make the customer-facing product more consistent, not to become another story customers have to understand.

The commercial model has evolved alongside the product. I introduced subscription tiers as the core workflow and the value of more advanced intelligence features became clearer. Packaging followed what the product could reliably deliver instead of a plan fixed at the outset.

The outcome so far

OS04 is live and in active development, with a working web platform, a native iOS experience and subscription billing. It now spans the journey from site attendance and compliance capture to permits, audits and AI-assisted operational records.

The clearest result so far is the shape of the product itself: lightweight where people have seconds to interact with it, rigorous where the business needs evidence, and increasingly intelligent where information would otherwise have to be read, rewritten or chased.

OS04 is still evolving, but its direction is established. It should understand how construction work actually happens and carry more of the administrative weight around it, without asking site teams to behave like software companies.