Industrial automation · Tech adoption
Describe the problem. We build the fix. It runs on its own.
Software and automation for plants, shops, yards, farms and fleets, ten to five hundred people. You tell us how the job really runs. We build what is missing.
Book a walkthrough See the work
Free. Thirty minutes. You keep the map.
- 30years on the floor
- 10 to 500people, the size we fit
- 5steps, stop after any
- Nonepenalty if you leave
The work
Four things we built. Different industries, same engineer.
Each one started as a problem somebody said out loud. All four are live: press the button and use the real tool.
Recommissioning a gas plant from twenty-year-old drawings.
The client bought a plant that had been shut down for years. 646 tags, thirteen questions each, before a single part could be bought. We built the system that answers them, tag by tag.
A 60-person fab shop, up for sale, and nothing written down.
The buyers loved the business and could not see how it ran. We interviewed 22 people, pulled out everything they knew, and built the whole operation into one package: flows, procedures, safety, ISO, maintenance, a legacy library. The deal closed.
A supply business that runs itself.
A teeth whitening supplier that sells to salons. One console reads the mail, chases the leads, counts the stock and writes the letters. The owner clicks only to send and to pay.
An end to end water delivery business, run from the truck.
One truck, 150 doors a week. The app asks every customer, builds the run, sends the invoice and takes the payment. The owner drives.
What we do
Plants, shops, yards, farms, fleets. Ten to five hundred people.
Full systems, or the one piece that replaces the spreadsheet that keeps breaking. Nothing off a template. Everything joined to what you already use, and once it is in, it runs without you standing over it.
Where this usually starts
Which one of these is your Monday?
Tell us the worst job in your week. We build it away.
Know what you have.
Today. A work instruction isn’t a document. It’s the laminated sheet at the station, the revision somebody penned in the margin, and the way the senior operator actually does it.
Built. The current version in one place, tied to the part and the station, so the person at the machine is looking at the one that is right today.
SOPs, work instructions, part numbering, document control, training material.
Know what you own.
Today. Purchasing isn’t a module. It’s the workbook three people email back and forth, the receiving slips in a binder, and the guy who knows which supplier is actually reliable.
Built. Those in one place, and the PO writes itself off what the job needs.
Inventory, BOMs, purchasing, sourcing, receiving, costing.
Know what’s happening.
Today. The schedule isn’t the whiteboard. It’s the whiteboard, the two jobs the supervisor is carrying in his head, and the phone call that moved everything an hour ago.
Built. The board runs off what is actually on the floor, so the answer to where is that order is the same answer no matter who you ask.
Scheduling, job tracking, WIP, quality records, maintenance, reporting.
Make it run without you.
Today. A quote isn’t a form. It’s the estimator pulling last year’s numbers, the approval sitting in an inbox over the weekend, and the handoff to production that happens by walking down the hall.
Built. Those steps connect, so the quote becomes the job and the job becomes the invoice without anyone retyping it.
Quoting through to invoice, approvals, notifications, handoffs between departments.
Make it safer and leaner.
Today. A near miss isn’t a form in a filing cabinet. It’s the thing three people saw, mentioned at the morning meeting, and nobody wrote down.
Built. Recording it takes fifteen seconds on a phone, so the pattern shows up before the incident does.
Safety records, incident tracking, lean implementation, kaizen, setup reduction.
Keep what your people know.
Today. The setup isn’t in the manual. It’s in the guy who has run that press for twenty two years and knows what it sounds like when it is about to go.
Built. That gets captured while he is still here, in his words, attached to the machine and the part, so the next person is not starting over.
Capture what your retiring guys know before it walks out the door.
Know what you just bought.
Today. You took on a site, or a yard, or a whole operation, and nobody has walked it with a list. No values, no vendors, no idea what still runs.
Built. Photograph a machine on a walk round. It identifies itself, finds the original vendor, checks rebuild or used, and files it. Purchasing ends up with every part, where to get it, and a reliability rating.
Asset register, parts and vendor sourcing, reliability rating, downtime cost, criticality ranking, spares.
Tell us yours.
Type the thing that costs you the most time in a week. It goes straight into the booking form, in your words.
Full systems, or the one piece that replaces the spreadsheet that keeps breaking.
How we do it
We draw your operation. Every step, every handoff, every spreadsheet.
This is the map. Lanes are who does the work. Colour is the tool it runs on. Red is where the job stops and waits for a person.
Order to invoice, as it runs today
A 90 person fabrication shop. Six handoffs, and every one of them is a person.
- 1 Quote waits for a signature 4.0 hrs a week
- 2 Quote re-typed into the job 6.5 hrs a week
- 3 Job written on the whiteboard 5.0 hrs a week
- 4 Floor asks what is next 3.5 hrs a week
- 5 QC paper walked to shipping 2.5 hrs a week
- 6 Shipping slip re-typed to invoice 7.0 hrs a week
28.5 hours a week spent waiting on a person.
Client details removed. On a bigger screen this is drawn as a map of the whole job.
One job, two ways
The handoffs stop being people.
Built so far
We do not sell you a system in a box. We fix the thing that is bugging you.
Then it snowballs. You fix the one that hurts, and it shows you the next one, and the one after that. Every job below started as a single problem. Different industries, same shape. Client names left out on purpose.
-
Energy and resources · asset recovery
A yard full of equipment nobody had catalogued.
WasA buyer took over an acquired facility and inherited the contents. No list, no values, no idea what still ran or what it would cost to bring back.
NowPhotograph a machine on a walk round. It identifies itself, pulls the original vendor, checks whether it can be rebuilt or sourced used, and files it with a reliability rating and a downtime cost. Purchasing ends up with every part and where to get it, instead of a yard and a guess.
Started as one walk-round app. It is now the asset register, the parts sourcing and the purchasing decision for the whole site.
-
Construction · flooring at building scale
Twenty floors, thirty units each, measured by hand.
WasSomebody counting square footage off drawings, guessing the waste factor, then chasing installers to find out what they actually used against what was booked.
NowUpload the drawings. It works out the area per unit, splits carpet, hardwood, floor tile, bathroom tile and backsplash, adds the waste factor, assigns installers and tracks booked against used all the way to job costing. Matching floor plans are grouped so the same crew repeats the same layout.
Started as a takeoff calculator. It became estimating, scheduling, crew assignment and job costing, because each one exposed the next.
Before you book
The questions a GM asks first.
- Do I have to replace my ERP?
- No. Most of our work sits around a system that already works and fixes the parts it never covered. We can build the whole thing when that is actually cheaper, and we will tell you when it is not.
- How long does a build take?
- Hours to days, depending on scope. We will not put a date on a job before we understand it. What we will say is that we move faster than anything you are used to, and you see working pieces every week rather than a reveal at the end.
- Who am I actually dealing with?
- Christopher. He runs the walkthrough, he writes the code, and he stays on the job through handover. A small team comes in as the work needs it. You are not handed to an account manager.
- What does it cost my people?
- A couple of hours from you for the walkthrough, then a short check-in each week while it is built. Your people keep working.
- What happens if it goes wrong?
- We don’t leave. The system has to run in your operation for an agreed stretch before the job is called done, and we go back and forth until it does.
- Do you have to come to our site?
- Most jobs run remote. When the job needs boots on the floor, we come. A walkthrough runs on a screen share, a phone camera in your operator’s hand, and whatever documents you already have. We are based in Kelowna, British Columbia and we work globally.
- What do I get from the walkthrough itself?
- A written map of your operation: every process, what it costs you in hours and dollars, what can be automated, and the order it pays back in, with each item priced. It is yours whether or not you build anything with us.
- Who owns the system?
- We keep the code. You keep your data and your freedom to leave. No license audits, no forced upgrades, export everything any time in an open format at no charge, and a thirty day exit with no penalty.
- How do you price it?
- Against the value of what the system replaces, not against hours. Every job is quoted on its own. Once a system is live, an annual licence covers hosting, support, upgrades and the changes that keep it current. It is the same rate for everyone, and you see both numbers in writing before you commit.
- Our data is a mess. Should we clean it up first?
- No. That is most of what the first two weeks is, and it is the same job whether you start now or a year from now.
Start with a walkthrough.
One session. We look at how your operation actually works, and you get a written map of every process, what it costs you in hours, what can be automated, and in what order it pays back.
Free. Thirty minutes. You keep the map.