Skip to content

JOURNAL

Updated on

NOTESFROM THE WORK

I publish when I have something to say, not on a schedule.

THE ANSWER

I write short pieces that answer one question and stop. What manual work really costs. When no-code stops paying off. What separates automation from artificial intelligence. Who owns the code I hand over. No announcements, no press releases: only what I learned by building.

Seen from above, two pairs of hands pass a blank sheet across a desk, beside a stamp and a tray.

AI-generated image

THE PIECES

  1. WHAT COPY-PASTE ACTUALLY COSTSA method for putting a figure on the time nobody counts.
  2. AUTOMATION OR ARTIFICIAL INTELLIGENCEHow to tell whether a step needs a rule or a model.
  3. ALTERNATIVES TO ZAPIERThe routes left when per-operation pricing stops adding up.
  4. CONNECTING A CRM TO GOOGLE SHEETS WITHOUT A DEVELOPERThree ways to get CRM data into a sheet, and the limit of each.
  5. WHEN NO-CODE STOPS PAYING OFFNo-code often pays off: the checks that tell you when it has stopped.
  6. WHEN A SPREADSHEET BECOMES A RISKThe moment a file stops being a document and turns into a system.
  7. WHERE THE PRICE OF AN AUTOMATION COMES FROMWhat actually pushes an automation quote up.
  8. WHICH PROCESS TO AUTOMATE FIRSTHow to pick your first process to automate, on your own.
  9. THE DIRTY DATA THAT BREAKS AN AUTOMATIONWhy automations fail on the data, and what to check first.
  10. WHO OWNS THE CODE I BUILD FOR YOURepository, accounts, credentials and documentation: what changes hands.
  11. WHICH KPIS ACTUALLY BELONG ON A DASHBOARDThe metrics that change a decision, and the ones that only look good.
  12. WHAT HAPPENS AFTER HANDOVERWhat support covers, and what changes if you go without it.