The finish path
A work order is turned in from the field in three taps.
Nobody ever decides to ruin a completion flow. It goes one reasonable field at a time until the crew is back on paper and the software is something the office looks at. So the count is a budget here, checked by a script on every build: a fourth thing on this path has to displace one of the three rather than join them, and a field drawn elsewhere on the card that blocks the checkmark counts as a tap even though it is not on the path.
What the technician writes is the record. It stamps their name and the time onto the card, and it is what the supervisor reads instead of asking.
A work order on a phone, walked through the finish: the card opens, a line saying what was done is typed into it, and the checkmark closes it. Three presses, counted on screen as they happen, with no signal needed to make them.
Pumps · today
Central battery
seal weeping · due Friday
Tank battery
gauge swap
Transfer pump
waiting on parts
- 1Open the card
- 2Write what was done
- 3Press Finished
The whole path is three taps, and a script fails the build if a fourth appears.
And the invoice end
What the crew typed on the cards is the month, already added up.
A cost line is a vendor, what it was for, a code off your own chart of accounts, and an amount, typed on the card by the person who bought it. There is no second system and no evening spent copying receipts into one: the statement is those lines, grouped by code, as they land.
A month’s statement, adding itself up: every cost line entered on a work order, grouped under the cost code it was coded to, with the month’s total at the foot and no spreadsheet in between.
Typed on the card, by the person who knows
- Packing and seal kit$1,281.32
Central battery · Pump Shop · 5230
The month, by code
- 5230 Valves & fittings$1,281.32
A job, from the phone call to the invoice, on one card.
A department gets a board. On it are projects, and a project is a stack of cards somebody works through: each card carries the kind of work it is, the phases that make it done, who ticked each one and when, and what it cost. Nothing is a status somebody types in a meeting later.
The board an outsider can reach
Every project has a link. Somebody with no account opens it, verifies their number with a texted code, describes the job, attaches photos from the phone in their hand, and it lands in the stack as an ordinary card with their name and number on it. The state of it is on that same link afterwards, so the follow-up call asking whether anybody looked never gets made.
The money, entered where it is spent
A cost line is a vendor, what it was for, a minor code and an amount, typed on the card by the person who knows. A finished card goes to the cost queue until it has a real figure, and the month's statement is built by the time you get to it, ready to close.
The forms are yours to shape
A form decides what a requester is asked and what phases the card arrives wearing, including sub-checks that must all be answered before the line above them can be ticked. Some forms stay internal and never appear on the public link at all.
A note is what somebody saw
Anybody on the board writes on a card, and up to three photographs go with what they wrote. What was found gets shown rather than described, next to the work, still there when somebody opens the job cold six weeks later.
Maintenance Request · Central battery
started by Sam O. · Sep 4, 10:02 AM
Request
requested by Theo B. · by link, verified · (575) 555-0142
Seal weeping at the stuffing box, needs a rebuild before Friday.
2 photos
- Drain and lock outTheo B. · Sep 4, 11:20 AM
- Pull and inspect sealTheo B. · Sep 4, 2:05 PM
- Rebuild and pressure test
Costs · 2
Filed through the board’s public link. No account, phone verified by a texted code.
One card, mid-job. The shape is the real one.
Watch it land
Somebody with no account files a job. It is on the board before they put the phone down.
On the left, a person your crew has never set up an account for: an operator on a lease, a landowner, a foreman from another company. On the right, the board that department already works off. Nothing is emailed, nothing is retyped, and nobody has to remember to open an inbox.
Their phone · no account
the district · Field Maintenance Maintenance
Nothing being worked yet.
Nothing waiting.
The board a department shares, waiting.
for the crew that fixes things
Work orders that finish in the field and add up at a desk.
Field software gets abandoned for paper the first week it asks too much of somebody wearing gloves, and the office inherits a shoebox. This is the other way: the crew finishes work on a phone with almost nothing asked of them, and the office reads a month that added itself up by cost code. Paste in the WhatsApp message that asked for the job and the order drafts itself, with the original words kept.
The order carries the job
Who asked, in their own words. Where it is, with directions behind the name and the coordinates kept as typed. What kind of work, from your own list. The AFE it is charged to, when the work is on one. Money on both sides: what it was estimated at, what it came to, line by line. A field nobody filled stays blank, because a blank is checked in five seconds and a guess lives for years.
Gloves, dirt and sunlight are the design brief
Every control on the field card is sized for a thumb in a glove and readable in direct sun on a cracked screen. Nothing on it asks for a decision that could have been made at a desk, and nothing on it is a dropdown of forty options. The crew is the constraint, not the last feature request.
No signal is the normal case
An order written at a dead pad is safe the moment the button is pressed: it stays on the phone, says it is waiting, and sends itself when coverage returns. Same for a cost line and the finish itself. Closing the app loses nothing, and a send that lands twice is caught by the server, not by luck.
The work that comes back on a schedule
A supervisor sets a standing order and it mints an ordinary work order on its day: same card, same three taps, same month. That is the whole of it. No meter triggers, no asset registry, and no second planner for a technician to keep up to date, because the calendar that has to be maintained is the one that stops getting maintained.
The month adds up, then closes
Spend by cost code, summed from the lines the crew entered where the money was spent, never retyped at a desk. A supervisor closes the month when it ends; anything that moves afterwards is called out beside the number that was quoted, and every correction to a line sits in that order's own diary.
Ops seats
A technician does not need a notes drawer, a calendar or a meetings history, and pricing them as though they did is how a crew of thirty never gets accounts at all. An ops seat comes with Office + Field, $50 a month on top of Office, and is $15 a month once the five seats the plan includes are taken. It holds the work orders and nothing else. Those five can be ops seats too, so a crew of three in the office and two in trucks pays the base and nothing more. A seat goes either way whenever you like.
And one refusal worth naming: the order has coordinates, the person does not. There is no GPS trail on technicians and there will not be one. Software the crew reads as surveillance stops getting opened, and then nothing above is true either.
the part nobody else does
The people who work for you do not work only for you.
Most tools assume everybody in a conversation belongs to the same company, and in a lot of businesses almost nobody does. So here, an independent brings their own subscription and joins any company that invites them, as many as hire them. No seat is bought for them, no second account exists, no company sees the work they do for anybody else, and when the job ends their notes leave with them, because the notes were always theirs.
Being invited into a company's work starts at Pro.
if you are the company
Invite the people who work on your sites without buying seats for contractors you do not employ. They see the work you share with them and nothing else. Somebody who leaves stops seeing it the moment you say so, and takes only what was theirs.
if you are the contractor
One subscription of your own covers every operator that hires you. Your board is your board across all of them, none of them can see the others, and the record of what you did on a job is still yours after the job.
Getting a company onto it.
Seats you hand out yourself
$150 a month covers the first 5 people, then $25 for each one after. The field, which is the work orders, the outside link and the ops portal, is $50 a month on top. A seat is one named person, added and removed by you, on one bill.
Storage pooled, not rationed
5 GB per seat, added together and left undivided: 5 seats is 25 GB for the whole company. One person with a camera full of site photographs uses what the others are not.
In from what you use now, out whenever
Bring existing notes in from another app, parsed on the device so nothing is uploaded while anyone is deciding. Your notes come back out as one file, on any plan, from the account page. That is a right rather than a feature.
Somebody leaves
Take their seat back and they keep everything they wrote, on the free tier, without access to what you shared with them. Nobody is locked out of their own work as a side effect of leaving a job, and no company loses the record of one.
Shared boards and departments
A board the whole company works off, split the way the company is. Set up a department for each part of the business, put the routine work on it once, and it comes back on its own schedule: daily, weekly, monthly, or the days you pick. One-offs get added as they turn up. The moment somebody checks a task off, it changes for everyone, stamped with who did it, when, and whatever they noted on the way past, so nobody has to chase anybody to find out where things stand.
What this is not, said before you find out.
Anyone choosing software for a company is looking for the catch, because there always is one. Here is the list, so the rest of the page is worth believing.
It is not a gantt chart
Projects here are cards, phases, budgets and a stamped record of who did what. There are no dependencies, no critical path, no burndown, and no resource leveling. If your company runs on scheduled work that software has to enforce, buy software that does. This is the layer where the work is actually written down.
It is not a wiki or a document store
Procedures, manuals and contracts belong somewhere built for them. What belongs here is what somebody noticed, what got decided, and what anybody agreed to do about it.
Your notes are not end to end encrypted
The server can read them, and has to: reminders and carrying an unfinished action to the next meeting are both things a server that cannot read your writing cannot do. Searching is not one of them, as it happens, because search runs in your browser over notes already loaded. If you have writing that nobody but you may ever decrypt, keep that writing somewhere else.
There is no SOC 2 report and no third-party penetration test
Those are real work and real money and we have not done them. If your procurement process requires one, we are not ready for you yet, and it is cheaper for both of us to find that out on this page.
We are a small company, not a vendor with an account team
There is no 24-hour rota and no assigned representative. There is an address that a person reads, and that person built the thing you are writing to them about.
The full account of how accounts are kept apart, what leaves the building and what we do not do is on the security page, written the same way.
the other two doors
And if it is one head, or an office without the field.
Start with one crew, one board, and the link.
That is the whole of the pilot worth running, and you will know inside two weeks. Put one department’s work on a board, hand the link to whoever keeps calling about it, and see whether the month is already built when they get to it. If it is, the rest of the company will ask for it without being told to.