oniru.ai7 min read
What clients actually mean when they ask for AI.
A request for AI is a budget and an expectation, not a requirement. Behind almost every one there is a specific, boring, buildable job worth finding first.
Notes from systems in production.
Practical writing on automation delivery, APIs and the operational details that make systems reliable.
Showing notes tagged field note.
Articles
oniru.ai6 min read
The automation nobody owns.
A workflow runs every night and nobody fully understands it. Working is not the same as owned, and the difference only becomes visible when it stops.
oniru.ai6 min read
When not to automate.
Agencies that build automation are badly placed to advise against it, which is why the advice carries weight when it comes from them. Six clear signals.
oniru.ai6 min read
White-label automation delivery without losing the client relationship.
Subcontracting technical work does not have to put the client relationship at risk. The protections are contractual and operational, and every one of them can be written down in advance.
oniru.ai7 min read
Quoting an automation project you have not built before.
A client wants a number by Friday for something you have never built. The cost is not in the build. It is in the unknowns behind it, and those are discoverable in an hour of questions.
oniru.ai7 min read
From a website form to a CRM record a salesperson can use.
Connecting a form to a CRM takes an afternoon. Deduplication, enrichment, routing and assignment are the rest of the project, and they are where the value actually sits.
oniru.ai7 min read
The automation failures nobody scopes for.
Automations rarely fail on the day they ship. They fail in week three, when a real person does something the demonstration never did. These are the cases that cause it.
oniru.ai6 min read
When a Zapier workflow stops being enough.
Most automation should stay in a no-code tool. This is how to tell a design problem from a missing connector from a genuine ceiling, and when a migration is not worth doing.
Have a client asking for something you can’t easily build?
Send us the requirement. We’ll tell you how we’d approach it, what it would require and whether it makes sense to build.
No pitch deck required. A rough description is enough.
Or write to [email protected]