The scope isn’t a feature list. It’s a list of decisions.
Every custom agent we build starts the same way: we write down every judgement the person doing this job currently makes, then decide one at a time which the agent takes and which it hands back. Get that list right and the build is straightforward. Skip it and no amount of engineering rescues the project.
In short: a custom agent is for a process specific to how you operate, where no product fits and a fixed workflow chokes on the exceptions. We map the decisions, build it read-only against real cases first, then give it write access behind approval gates that come off one at a time.
The decision inventory
We sit with whoever does the work and record every point where they choose something — including the choices they don’t notice making, which are usually the important ones. A typical list runs to twenty or thirty entries for a process people describe in four steps.
Then each one gets sorted into three buckets:
THE AGENT DECIDES
Judgements with a clear right answer that a person can verify afterwards. Classify this request, extract this figure, match this to that record, pick the next step from these four. The bulk of most processes lands here.
THE AGENT PREPARES, A PERSON RELEASES
Anything costing money, contacting a customer, or hard to reverse. The agent does the work and someone approves the outcome. Gates here get removed individually once accuracy has held across enough real cases.
NEVER THE AGENT
Judgements affecting someone’s money, employment, credit or care, and anything a person would have to justify later. The agent can gather and recommend; it doesn’t get the last word.
AND ONE MORE COLUMN
How we’ll know it was right. Every decision in the first two buckets needs a check — a sample someone grades, a downstream signal, an override rate. Without it there’s no way to improve the agent or notice it drifting.
Read-only before write access
Once the inventory exists, the agent gets built and pointed at real cases — producing what it would have done, writing nothing. You compare its decisions against what your team actually did, case by case.
Disagreements at this stage are cheap and instructive. About half turn out to be the agent being wrong, and about half turn out to be an undocumented rule nobody had mentioned. Both are worth finding here rather than in production.
What we won’t do
Build an agent for a process that runs the same way every time
That’s a workflow — cheaper, more predictable and easier to test. We’ll tell you when yours is one, and it happens often enough to mention.
Give it a borrowed admin login
Its own service account, narrowest access that lets it finish, everything it touches logged and tagged so a bad run can be undone. Retrofitting that after an incident is considerably harder.
Start without a success measure
Even a rough one. An agent nobody can score is one nobody can improve, and it will quietly get worse without anyone being able to prove it.
Roughly six weeks
Two weeks watching and writing the inventory, two running read-only against real cases, two live behind approvals with logging and rollback tagging in from the start. More systems, or rules that exist only in someone’s head, lengthen the first phase rather than the last.
What our clients say
The businesses we’ve built for, in their own words.
★★★★★
“When I approached Abedin Tech with my land share selling plan, I wasn’t sure how it would work. But thanks to their precise strategy and powerful marketing, my business is now thriving. They truly understand their clients’ needs and go above and beyond.”
Owner, Richland Properties
Real Estate
★★★★★
“I approached Abedin Tech to develop my website with several specific functionalities. Their team delivered exactly what I envisioned, creating a beautifully designed website that met all my requirements. I highly recommend Abedin Tech.”
Rohit
Owner, Shop from China
★★★★★
“The decision to partner with Abedin Tech was the best decision we made. Our site looks great, our traffic is through the roof, and our sales are better than ever. Abedin Tech is the perfect digital partner that offers what is beyond your expectations!”
James Anderson
★★★★★
“We had an idea but no sense of direction. With each step of the way, Abedin Tech guided us and turned our vision into a beautiful website with functionality. The outcome is evident by the numbers!”
Isabella Scott
Which process would you struggle to hand to a new starter?
That difficulty is the decision inventory, and it’s exactly what makes a process a candidate. Describe it and we’ll tell you whether it wants an agent, a workflow, or a written procedure first.
By writing a decision inventory before anything is built: every judgement the person doing the job currently makes, including the ones they do not notice making. A process people describe in four steps usually produces twenty or thirty entries. Each is then sorted into what the agent decides, what it prepares for a human to release, and what it must never decide — plus how we will know it was right.
What runs read-only first, and why?
The agent itself. It works against real cases and outputs what it would have done without writing anything, so you can compare its decisions with your team’s. Roughly half the disagreements turn out to be the agent being wrong and half turn out to be an undocumented rule nobody mentioned. Both are far cheaper to find at this stage than in production.
When is a workflow the better answer than an agent?
When the process runs the same way every time. A fixed workflow is cheaper, more predictable and easier to test, and we say so when that is the honest answer. An agent earns its cost on the exceptions — the missing field, the unusual request, the case that fits no category.
How long does a custom agent take to build?
About six weeks: two spent watching the process and writing the decision inventory, two running read-only against real cases, and two operating live behind approval gates with logging and rollback tagging built in from the start. More connected systems, or rules that live only in someone’s head, extend the first phase rather than the last.
