Stonecut

Building a place for my own products

I founded Stonecut after years of working across engineering, product, design and independent client work. I had taken many ideas from ambiguity to a shipped result, but usually inside somebody else’s organisation or within the boundaries of a project.

Stonecut is the structure for taking my own ideas further than a prototype. It is an independent product company through which I can discover a problem, decide whether it deserves sustained attention, build the product and remain responsible for what happens after release.

That continuing responsibility is the point. The work is not only making software; it is choosing what to pursue, putting it into people’s hands and allowing real use to change the next decision.

Owning the whole loop

Building through Stonecut means owning the connected system around a product: research, strategy, design, engineering, distribution, commercialisation, support, measurement and iteration.

Those parts cannot be separated cleanly in a small product company. A positioning decision changes the interface. A support conversation can reveal a product constraint. The commercial model affects which behaviours matter, while the way a product is distributed changes what new users need to understand first.

Working across that whole loop draws on the same product-engineering range I have developed elsewhere, but with a longer feedback cycle and nowhere to hand the difficult decisions off.

From projects to products

Project work asks whether I can understand a problem and deliver a useful result within a defined engagement. Product ownership keeps the harder questions open for longer: is this problem worth solving, for whom, how should the product behave, how will it reach them and what does actual use reveal next?

Stonecut gives me a place to answer those questions through sustained work rather than a sequence of disconnected experiments. It also makes restraint important. Deciding not to build something, narrowing a proposition or changing direction when the evidence is weak are part of operating the company, not failures to produce output.

A deliberately broad umbrella

Stonecut is not tied to a single industry. It is a home for focused software products that may sit in entirely different categories, connected by how they are researched, built and operated rather than by one market label.

That distinction matters because a company should be able to learn from one product without making that product’s category its permanent boundary. Stonecut can hold several products over time without asking them to share a customer, workflow or brand.

Products as experiments with consequences

A Stonecut product is not complete when a prototype looks convincing. It has to contend with real infrastructure, users, distribution, positioning, analytics, operational decisions, support and payments where the model calls for them.

Those consequences make the learning useful. They expose whether the problem is frequent enough, whether the workflow survives outside a demo, whether people understand the value and whether the product can be operated responsibly. They also force decisions about what not to build and where additional complexity is no longer earning its place.

The system I use to build matters because it preserves that judgement while allowing a solo company to move at a useful pace. Small releases, explicit product behaviours and recurring verification create continuity between exploration and operation.

OS04 as one example

OS04 is Stonecut’s site-operations product for construction. It shows one product in depth: the field constraints, connected web and mobile workflows, compliance records and AI-assisted operational work involved in turning a broad problem into live software.

Read the full OS04 case study.

OS04 demonstrates what Stonecut can make, but its category does not define the company. Stonecut is the broader structure for repeatedly finding, building and operating products from first principles.