Herendil
Applied AI that gives your team its time back.
Herendil is a small consultancy for companies that want AI working inside their own operations. We find the hours that go to searching, status updates and handoffs, then build agents that take that work on, one workflow at a time.
Scroll to see the week change
A typical week
IllustrationMon
Standup
Find Q3 numbers09:30–11:00
Check Q309:30–10:00
+60 minCustomer call11:00–12:00
Status update13:00–14:00
Review update13:00–13:30
+30 minHandoff to ops14:00–15:30
Check handoff14:00–14:30
+60 minPlanning16:00–17:00
Tue
Standup
Find a decision09:30–10:30
Read answer09:30–10:00
+30 minProduct review10:30–12:00
Reconcile sheets13:00–15:00
Review gaps13:00–13:30
+90 minOne-to-one15:00–16:00
Meeting notes16:00–17:00
Edit notes16:00–16:30
+30 minWed
Standup
Board deck prep09:30–11:30
Review deck09:30–10:00
+90 minInterview13:00–14:00
Repeat questions14:00–15:30
Vet answers14:00–14:30
+60 minTeam retro16:00–17:00
Thu
Standup
Chase approvals09:30–10:30
Sign off09:30–10:00
+30 minCustomer workshop10:30–12:00
Support handoff13:00–14:30
Check handoff13:00–13:30
+60 minWeekly report14:30–16:00
Edit report14:30–15:00
+60 minHiring sync16:00–17:00
Fri
Standup
Find the contract09:30–11:00
Check terms09:30–10:00
+60 minAll-hands11:00–12:00
Update the CRM13:00–14:00
Check CRM13:00–13:30
+30 minCustomer visit14:00–16:00
Week summary16:00–17:00
Send recap16:00–16:30
+30 minHow agents give time back
1Before
A normal week
The grey is work about work. Someone looks for last quarter’s numbers, writes the same update for three audiences, and walks the next team through a handoff.
2With agents
Agents take the repetitive part
An agent gathers the numbers, drafts the update from what already happened and prepares the handoff. It answers from the company’s own documents and decisions, the company brain. People still review and decide.
3After
The time comes back
Each task shrinks to the part that needs a person, and the rest of the hour is free again. This week is an illustration. In an engagement we count the hours in your real one.
The shape of an engagement
One workflow, from the first conversation to handover.
This is a typical shape. Some workflows need four weeks, others twelve, and you see the plan before we start.
Understand
We sit with the people who do the work, map where their week goes, and agree on one workflow to change.
Build one workflow
We build the agent with that team, inside the tools they already use, and put it on real cases early.
Measure
We count hours and errors before and after, with the team’s own numbers, and fix what the count shows.
Hand over
Your team gets the code, the prompts and a runbook, and runs it without us. Then we can pick the next workflow.
Notes
Short pieces on applied AI, written as the work happens.
- 6 minWhere the week goesBefore choosing a model, count the hours spent finding things, asking twice and passing work along.
- 9 minA company brain is mostly permissionsAn agent that answers from company knowledge first needs rules for what it may read and who may see the answer.
- 5 minMeasure one workflow before you build tenHow we count time before and after, and why the team being measured does the counting.
- 8 minInference cost is a design inputLatency and price per call decide which steps an agent should take and which it should leave to people.
Find a time
Thirty minutes about one workflow.
Bring a workflow that takes more of your team’s week than it should. We’ll talk through whether an agent could take it on, and what we would try first.
- You describe the workflow and who does it.
- We ask where the hours go.
- We say whether we can help, and how.
When it does, you’ll pick a 30-minute slot right here. Nothing on this page sends or stores anything yet.