Teams and use cases

How a team's work runs with agents.

Each kind of work is written down as a workflow: what starts it, the steps, who does each step, where a person approves, and what proves it is done. Pick a team to see one. The same five parts hold for every team.

Pick a team. See who does each step.

Read each workflow from top to bottom. Each step says which steps must finish before it. Only the steps that need judgment go to an AI agent.

Engineering

A ticket becomes a merged code change

How Widal.Factory runs a ticket for an engineering team.

5 steps: 1 by an AI agent, 3 by plain code (1 is a check), 1 by a person.

A person. Decides and approves.

AI agent. Does the steps that need judgment.

Plain code. Does the fixed steps and runs the checks.

Starts when (a person starts it)

An engineer hands a ticket to the factory in the tracker.

  1. Step 1.Plain code

    Prepare the workspace

    The factory makes a clean copy of the code for this ticket and gives the agent the ticket and your rules.

    Starts when the work starts.

  2. Step 2.AI agent

    Write the change and its tests

    The agent reads the code, writes the change, and asks on the ticket when something is unclear.

    After step 1.

  3. Step 3.Fixed check

    Run your tests

    Your tests run on the change, as on any other. If they fail, the agent gets the result and fixes the change.

    After step 2.

  4. Step 4.The engineer who owns the ticket(a person)

    Review and merge

    Nothing reaches the main branch without a person.

    After step 3.

  5. Step 5.Plain code

    Close the ticket and record the run

    The factory closes the ticket, cleans up, and records the time and the cost in the hub.

    After step 4.

Done when

The change is merged into the main branch and the ticket is closed.

Proof kept: The link to the merged pull request, kept with the ticket.

Your team is not on the list?

Tell us the work your team repeats every week. We draw its workflow with you, with your own checks and approvals.

Book a call

Five parts, in every workflow.

This is the model behind each diagram. The right column shows how Widal.Factory does it for engineering.

Start
What starts the work: something that happens in one of your systems, a set time, or a person who hands the work off.
An engineer hands off a ticket in Linear or GitHub Issues.
Steps
Each step is done by an AI agent, by plain code or by a person. A step names the steps that must finish first, so steps that do not depend on each other can run at the same time.
One fixed workflow, from ticket to merged change.
Check
A script that tests a result and gives the same answer every time. If the check fails, the agent tries again, up to a set limit. Then a person takes over.
Your tests and CI run on every change.
Approval
The point where the work stops and waits for a named person. Nothing final happens before it.
An engineer reviews and merges every change.
Done
The last step tests the proof that the work is finished, such as a merged change, a filed record or a confirmation from the other party. The proof is kept with the work.
A ticket is done when its change is merged and the ticket is closed.

Every company

The teams every company has. The agents take the repeat work, and people keep the decisions.

Engineering

Tickets become reviewed code changes.

See its workflow

What the agents do

  • A ticket becomes a pull request, with tests
  • Failing checks fixed and branches kept up to date
  • Security and dependency updates
  • Follow-up work after an incident

An example check

Your tests and CI pass, and a person reviews and merges the change.

Product

Customer input becomes clear specs and tickets.

What the agents do

  • Feedback from calls and tickets sorted into themes
  • A spec drafted from a problem statement, with open questions
  • Specs split into tickets the factory can build
  • Release notes from what was merged

An example check

Every spec names the problem, the user and how success is measured.

Sales

Less time on research and paperwork, more time with buyers.

What the agents do

  • An account brief before every call
  • Call notes written into the CRM
  • Proposals and security questionnaires drafted from approved answers
  • Follow-up emails drafted for a person to send

An example check

Every answer comes from an approved source, and nothing is sent without a person.

Marketing

Content and reports, with every claim checked.

What the agents do

  • Articles and pages drafted from your own material
  • Campaign and website reports each week
  • Event and webinar follow-up
  • Pages kept up to date when the product changes

An example check

Every claim links to a source, and the brand and legal rules pass.

Customer support and success

Faster answers, from your own knowledge base.

What the agents do

  • Answers drafted from the help center and past tickets
  • New tickets sorted and sent to the right person
  • Bug reports turned into engineering tickets
  • Account health summaries before a renewal

An example check

Every answer cites an approved article, and a person sends it.

Finance and operations

The monthly close and the paperwork around it.

What the agents do

  • Invoices matched to orders and payments
  • Reconciliations prepared for the monthly close
  • Spend reports by team and vendor
  • New vendors set up with the documents you require

An example check

The numbers add up to the ledger, and a person approves every payment.

People

Hiring and onboarding without the busywork.

What the agents do

  • Job descriptions from the team's needs
  • Interview notes summarized against the scorecard
  • Onboarding checklists and accounts for new hires
  • Answers to policy questions, with the source

An example check

Every answer points to the current policy, and decisions about people stay with people.

Life sciences and healthcare

The teams that work under FDA, HIPAA and GxP rules. Here the checks and the sign-off matter most.

Quality

Quality records drafted from the evidence.

See its workflow

What the agents do

  • Deviations and CAPA records drafted for a person to approve
  • Change control packages
  • SOP updates when a process changes
  • Audit preparation

An example check

Every required field is filled, and every reference points to an approved document.

Regulatory affairs

Submission documents drafted from your sources.

See its workflow

What the agents do

  • Submission sections drafted, with citations
  • Labeling changes tracked across documents
  • New guidance from regulators summarized for your products
  • Answers to agency questions drafted

An example check

Every statement cites a controlled source.

Clinical operations

Study documents complete and on time.

See its workflow

What the agents do

  • Site and study documents prepared and tracked
  • Trial master file checked for missing documents
  • Monitoring visit reports drafted
  • Site feasibility summaries

An example check

The required documents are present and their versions are current.

Safety

Adverse event cases, on the clock.

See its workflow

What the agents do

  • Adverse event cases drafted from the intake
  • Medical literature screened for safety reports
  • Periodic safety reports prepared

An example check

The reporting clock is tracked and the minimum case data is present.

Patient support and access

Patients get to therapy faster.

See its workflow

What the agents do

  • Benefits checks
  • Prior authorization packets prepared
  • Appeals drafted after a denial
  • Patients told the next step in plain words

An example check

The payer's required fields and deadlines are met.

Revenue cycle

Clean claims and fewer denials.

See its workflow

What the agents do

  • Coding reviewed against the visit notes
  • Denied claims sorted, with a fix for each
  • Eligibility checked before the visit

An example check

Every code is backed by the note, and the payer's rules pass.

How a team is added.

A package per team

Each team gets a package: its agents, its written workflows and its checks. A company installs the packages it needs and leaves out the rest.

Roles like job descriptions

Each agent has a written role: what it may do, which systems it may read, and who it reports to. A person on the team is responsible for it.

Adjusted to your company

No two companies run a team the same way. Your procedures become the workflow, and your acceptance rules become the checks.

One hub for all of them

Every team shows up on the same page: what the agents are doing, what waits for a person, and how speed and quality change.

Tell us which work you want to hand off first.

Book a call