The work that still runs on memory, chat threads, and typing things twice.
STATE · MANUAL
BEFORE · AFTERSTATE · MANUALSTATE · SYSTEM
PROCESS / 01 · SYSTEMOrder→Typed line by line→Invoice
PROCESS / 02 · SYSTEMStock→Memory→Decision
PROCESS / 03 · SYSTEMQuote→Entry→Re-entry→Sent
PROCESS / 04 · SYSTEMWhatsApp→Messages→Calendar
PROCESS / 01 · MANUALOrder→Typed line by line→Invoice
PROCESS / 02 · MANUALStock→Memory→Decision
PROCESS / 03 · MANUALQuote→Entry→Re-entry→Sent
PROCESS / 04 · MANUALWhatsApp→Messages→Calendar
PROCESS / 01 · MANUAL
The invoice someone types
Every line, entered by hand, every time an order arrives.
Order→Typed line by line→Invoice
PROCESS / 02 · MANUAL
The purchase someone decides from memory
What to produce or buy, decided by habit instead of by a count.
Stock→Memory→Decision
PROCESS / 03 · MANUAL
The quote someone enters more than once
The same numbers, copied into the same system, again.
Quote→Entry→Re-entry→Sent
PROCESS / 04 · MANUAL
The booking that starts in a WhatsApp chat
An appointment negotiated message by message, then written into a calendar.
WhatsApp→Messages→Calendar
Processes like these live in operations, finance, sales, administration, purchasing, scheduling, or customer service. The department matters less than the repetition. If a person repeats it, a system can probably hold it.
Method
Before I build anything, I find out what it costs you now.
Most automation work can’t prove what it saved, because nobody measured the process before building it.
01
Observe
The process as it runs today
02
Measure
Hours, money, or errors
03
Document
Process and cost, in writing
04
Decide
What deserves to become a system
Automate
Fix
Delete
Don’t build
05
Build
At the fixed price in the plan
06
Measure again
Same count, after launch
The count can also show that a step should be deleted instead of automated, that the process should be fixed, or that it isn’t worth building. When it does, the plan says so.
One client. One process. Figures reported by the client: their own estimate of the time the booking process took each day, before and after the system.
Twelve months after launch, the system had not needed me once.
You’ll work with me, the person responsible for the system.
I’m Tomás Posada. I work on my own from Medellín, Colombia, and I do the work from start to finish. This is how continuity works:
Who builds it
Tomás Posada
Medellín, Colombia
Independent. One person, from start to finish.
My role
I watch the process, count what it costs, write the plan, build the system, and count again after launch.
What’s yours
The system, built to run without me
Every account, created in your name
Every workflow, with its own explanation inside
An alarm for every subscription and renewal
What’s mine
The same alarms, on my side
Contacting you before anything lapses
Wellen, after launch: 12 months without needing me once
Delivered work
Twenty-five projects delivered since 2023.
REGISTRY · COUNTS ONLY
25projects delivered
17automation projects
8marketing projects
Selected delivered work
TPJ · REG 01Manzato Vital
A robot that turns a Google Sheets order matrix into draft invoices in Siigo.
Delivered
TPJ · REG 02Replenishment Planner
A planner that tells the same team what to produce or buy, and when.
Delivered
TPJ · REG 03Intelligent Training
A single-entry quoting system built inside Microsoft Dynamics 365.
Delivered
TPJ · REG 04Wellen Home Massages
WhatsApp and calendar bookings.
Delivered
These are counts of delivered work, not measured outcomes. The only measured result shown on this site is the Wellen case above.
The diagnostic
AUDIT · FIXED PRICE
INPUT · 1 WEEK · OBSERVATION
Every project starts with one week of measurement.
I watch the person who does the work, with screen sharing when needed, and read access to the history in the CRM, the spreadsheet, or the inbox. Then I count what the process costs now: hours, money, or errors.
01 · The process as it currently runs
02 · What the process currently costs
03 · A fixed-price implementation plan
The plan also identifies steps that should be deleted rather than automated.
If the count shows the process should be fixed instead of automated, or that a build is not worthwhile, the plan says so.
You can stop after the diagnostic and keep the plan.
From the diagnostic to the second count
You start here
Diagnostic
One week
USD 150
Plan in writing
Within five business days
Build
At the fixed price in the plan
Launch
Count again
After launch, I repeat the count the same way.
Diagnostic and build: usually 4 to 8 weeks
Start a conversation
Talk to me directly.
CHANNELS · 02
Call
Free 20-minute call
You’ll talk with me, the person who would build the system.
