Custom software
A system that fits around your operation
We Are Potato designs and builds internal systems for operations that live in spreadsheets, generic ERPs and WhatsApp today. The model below is an example of what we would build.
Who it's for
- Manufacturers with their own plant
- E-commerce with a distribution center
- Service companies with field teams
Pick the company closest to yours
See how it would work for your company
Fictional company and data. The shape is that of a system we would build.
See something close to your operation?
Tell us about itBy area
What the system covers in each area
Marketing and sales
- Campaigns and channels in one place
- Acquisition cost per channel
- Stock available to sell
- Campaigns that respect what the plant delivers
Stock and distribution center
- Orders from intake to dock
- Vans and today's routes
- Stock cover in days
- A warning before it runs out
Plant
- Machines and what each one is doing
- Production orders and deadlines
- Inputs that stall the line
- Efficiency per shift
We've done this outside the model too. See the cases
Alternatives
Why not off-the-shelf software
Off-the-shelf or a generic ERP
It's built for the average company. Yours has a labeler that stops without labels and a kit that depends on it. The generic one doesn't know that, so the rule becomes a patch around it.
Spreadsheets and WhatsApp
Fine until volume doubles. The answer lives in the head of whoever you ask, and the label order goes out with no date because nobody saw the machine stop.
A vendor that delivers and leaves
It delivers the scope and leaves. An operations system changes every week, and whoever built it needs to stay close.
Process
How we get there
- 01
Diagnosis
We follow the operation and draw the flow that costs the most today.
1 to 2 weeks
- 02
First flow live
One flow, running on real data, before anyone talks about a full system.
4 to 6 weeks
- 03
Steady evolution
The second flow comes in, then the third. Each cycle, the system covers more of the operation.
Monthly cycles
Underneath
What sits underneath
For whoever will maintain the system.
- 01
Integrations and APIs
The machine and the operator's log come in through an integration. Each source is a connection we have to keep alive.
- 02
Reliable data
Every step of an order keeps a time: paid, picked, packed. Without that record, a delivery date is a guess.
- 03
Permissions
Who can see and who can act are separate lists. Whoever sees the stopped labeler is not the person who decides to buy labels.
- 04
Business rules
The Mother's Day campaign only sells what stock can carry. That rule lives in the system, not in the memory of whoever remembers to check the shelf.
- 05
History and audit
When the label delivery changes, the kit order moves. The history keeps who approved it, what changed and when.
Is your operation still living in spreadsheets?
Tell us about it