What we build

AI agents and data pipelines that run inside your own systems

Every agent hands its work to a named person on your team, and we log each output with that person's decision.

For operations and data teams

Document and data pipelines

Documents and data arrive by email and through partner portals, and someone checks each source by hand. When the data and documents an agent needs aren't in one place yet, this work comes first.

Tony's background: at Enterprise Community Partners, he led data engineering and advanced analytics for a 1,200-person national nonprofit and cut time-to-reporting from hours to under 30 minutes. More about Tony

  • Picks up documents and data that arrive by email or through partner portals, and files each one by type in a single repository with permissions and version history. Each file is tagged with where it came from, what kind of document it is, its as-of date and its language.
  • Shows each period which files have arrived and which are late, with alerts and a status page. Your team stops checking every source by hand each day.
  • Pulls scattered spreadsheets and data into a single database.
  • Moves sprawling shared drives into repositories where each person has their own login and access depends on their role. Every file gets version history.
  • Automates recurring data refreshes through your licensed data feeds. Where a license or a provider's terms don't allow automation, we build a version that a person on your team starts and watches.
BUILT-IN LIMITS

Sensitive records are flagged for you and move only when you say so.

For research teams

Research and monitoring agents

Analysts dig out old notes and recheck what changed before every review. And between reviews, the inputs sitting in your models go stale.

Tony's background: at Fidelity, he built default-probability models and the credit risk infrastructure that watched $70–120B in trading exposures. At Semanteon Capital, he designed systematic trading strategies based on deep learning algorithms, ran them with live capital, and built the data platform they sat on.

  • When an analyst starts work on a company or a file, the agent pulls up the earlier notes and comparable cases. It also lists what's new since the last review, then drafts an update for the analyst to correct.
  • Watches new reports and data for everything you track.
  • Flags model inputs that current evidence calls into question, and points to the ones most likely behind the difference.
  • Proposes model inputs from current data and records its reasoning.
  • Every time an analyst changes a judgment call in a model, the agent records the change and the analyst's reason.
BUILT-IN LIMITS

Nothing is saved without an analyst's approval.

The agents propose and flag, and the analyst decides.

For client service teams

Drafting agents for client communications

The same client communications get rebuilt by hand every period, in every language you work in. Routine requests sit in a shared inbox until someone has time to answer them.

Tony's background: at Commsafe AI, he built LLM systems and agents that flagged high-risk communications in real time.

  • Generates recurring client communications from live data on request, in each of your languages. Every figure carries its as-of date.
  • Approved or regulated wording stays fixed. The agent fills in only the data fields, and flags any suggested wording change for your compliance team.
  • Writes draft replies to routine requests from your current documents and cites its sources. Each draft sits unsent until a named person edits and sends it.
  • Skips any message that's unclear or outside its scope, and leaves it for a person.
BUILT-IN LIMITS

Drafting agents never hold permission to send.

Their access is scoped to the specific mailboxes and systems they work in.

How every build runs

12 rules every build follows

If your risk or IT reviewers want these in writing before a call, send them a link to this section.

Your systems and your data

Where does our data go?Inside your environment. Everything runs in your own cloud and systems. Your data stays there and isn't used to train any model.
What can each component touch?Least privilege. Each component gets only the access it needs, scoped to the specific mailboxes and systems it works in. For example, a drafting agent can read and draft but can't send.
Can we change model providers later?Model-agnostic. Where we choose the model, it sits behind an adapter, so the provider can change.
Who owns it afterwards?You own it. Deliverables become your property on payment. Every agent ships with an operating guide, plus runbooks and knowledge-transfer sessions.

Who decides

Who's accountable for what goes out?People approve. Agents draft and flag. Nothing an agent drafts goes out or gets saved until a named person on your team approves it.
Can we reconstruct what happened?Everything logged. We record the prompts, retrieved sources, model version, output and the reviewer's action, and you can export the log for compliance and supervision.
Does it get better, and whose data is that?Improves with use. When your team corrects a draft or decides on a flag, we capture that decision and feed it back in. It stays your data.
Where do you stop?Limits. Automation stays inside each provider's terms of use. Where a license doesn't allow it, we build a version a person on your team runs. We recommend and you decide.

What you commit to

What do we commit to before the build?Gated start. An environment assessment of about a week confirms platform, data access, scope, acceptance criteria and timeline before you commit to a build fee. If an assumption doesn't hold, you get an adjusted scope, and if you decide not to go ahead, the engagement ends there. If you've already had the full assessment, it covers this step and the build starts straight away.
How is it priced?Fixed fee per phase. Each phase has defined deliverables and written acceptance criteria, and you authorize each one on its own.
How do we know it works?Proven before handover. Before you accept a phase, we demonstrate it in your environment against agreed test cases, then run it under supervision for a set period. Where it's relevant, we also compare the output side by side with manual work.
What happens once we've accepted it?Warranty after acceptance. Ongoing support is optional and month to month.
Engagement

How an engagement runs

Phases build on each other: get the data and documents right first, then build the agents that read from them.

1
ABOUT 1 WEEK · FIXED FEE

Assess

You decide: go ahead, or stop here.

2
TYPICALLY 3–8 WEEKS PER PHASE · FIXED FEE

Build in phases

You authorize each phase on its own.

3
OPTIONAL · AFTER ACCEPTANCE

Operate

Support is your choice, month to month.

Tony Daggett, founder and principal of ARDInsights
Led by Tony Daggett

Tony leads every engagement and is in every working session. ARDInsights engineers build alongside him. More about Tony and the team

After handover

Optional monthly support

You can run what we built yourself, with the operating guide and runbooks. Or keep ARDInsights on monthly support.

Monitoring and a monthly health report.
Repairs when sources or third-party services change.
Model upgrades: we move you to new model versions and re-test before you switch over.
Security updates, plus scheduled changes to passwords and access keys.
Small additions within the agreed scope.
A quarterly review.

Tell us what you want built.

A free 30-minute intro call. You'll leave knowing whether it fits, even if we never work together.

Book a free intro call