Why  ·  How  ·  What
It starts on the tools

I'm a joiner. Not an engineer.

Thirteen years running my own joinery business. Close to five thousand jobs, priced by hand, on spreadsheets I built myself. I know exactly where the time goes.

13Years running the business
5,000Jobs priced by hand
2People at the start
The problem I live

I type every job seven times over.

Estimate, order, invoice, schedule, each in a different tool. So I type the same job again and again. For a joiner, that's about eight hours a week, gone.

Why  ·  How  ·  What
So I made a bet

I can't really code. So I built something that can.

No team, and no budget. Just one question: why not build the whole thing with AI? So I did.

How it is built

One AI can write code. Trusting it is the hard part.

How it remembers

It learns from the mistakes it makes.

Every fixed mistake is remembered, so a repeat is far more likely to be caught.

0 things remembered0 connections0 mistakes it learns from
The scale, today

Just me. And a factory of agents.

0Specialist agents
0Knowledge commits
0Documents of memory
0Feature areas live in testing
Why  ·  How  ·  What
What it does

Enter the job once. It flows everywhere.

The estimate becomes the order, the invoice, the schedule. Entered once, seen by everyone.

One connected job

One estimate feeds the whole job.

Price it once. It flows to materials, orders, invoices, and the schedule.

What I am building

Sixty four feature areas. One connected platform.

37 live in testingthe rest in progress
Rugene

I look forward to sharing more with you.

Coming to a computer near you.

tap to continue
Paused