Five agents. Five approvals. Software your team can review.
Dextre takes a request through requirements, design, coding, testing and deployment using five specialized AI agents. After every stage a person approves or declines. Every decision, tool call and test result is recorded, so the work stays reviewable.
Request a demo →Dextre is a governed AI software delivery platform: five AI agents carry a piece of work from a plain-language request to a pull request, and a person approves every stage.
Nothing moves forward until a person approves it.
A job always moves through five stages in the same order, each run by its own agent and each followed by a person’s approval.
- 01RequirementsReads the request and any files or pages it names, and writes the requirementsYou approve the requirementsApproved
- 02DesignChecks the relevant documentation and proposes the approachYou approve the approachApproved
- 03CodingWrites the code in an isolated workspace, then builds and checks the appYou approve the code changes, shown as a diffApproved
- 04TestingTests are run by a real test runner and the results are reported as they came backYou approve the quality verdictApproved
- 05DeploymentPrepares delivery, including the build pipeline and a deployment runbookYou approve go-live, which only an administrator can approveAdministrator
Decline any stage and the work goes back to the same agent with your comments attached. Each stage starts with fresh context and takes the previous stage’s approved output as its input, so a later stage never builds on something nobody approved.
Requirements agent
Reads the request and any files or pages it names, and writes the requirements.
What you approve: The requirements
Approve to move on, or decline to send it back with your comments.
Example request
Add an export option to the monthly report.
- No decisions yet.
One idea. One prompt.
A farmer describes the app they need in plain language. Dextre builds a first version to review, then adds to it one prompt at a time.
Three checks you can try.
Agents with only the tools they need
Each agent gets only the tools its stage needs. Rules check every action before it runs, and results are scanned for secrets afterwards.
- ✓write code in the isolated workspace · allowed
- ◉result scanned for secrets
- ✓build and check the app · allowed
- ◉result scanned for secrets
- ✗edit the build pipeline · blocked before it ran: a tool of the deployment stage, not this one
Test results you can trust
A test counts as passed only when a real test runner reports success. Dextre shows the runner’s result, not an agent’s own summary.
Quality verdict: not passed, as reported by the test runner
Your choice of AI model, with spend limits
Run Dextre on the AI providers your organization approves, pick a model for each stage, and cap what a job and each stage can spend.
| Stage | Model | Stage cap | Spent of cap |
|---|---|---|---|
| Requirements | 30 | 12 of 30 | |
| Design | 30 | 18 of 30 | |
| Coding | 60 | 34 of 60 | |
| Testing | 40 | 9 of 40 | |
| Deployment | 20 | 0 of 20 | |
| Whole job | 200 | 73 of 200 |
A full record of what happened.
Every tool call, blocked action and human decision is recorded, and the record is protected so any tampering can be detected.
Everything you do on this page is added here. Try changing an earlier entry and the tamper check flags it.
- 01Example: Requirements approved by an approverrecorded
- 02Example: Design declined and returned to the same agent with commentsrecorded
- 03Example: Design approved by an approverrecorded
What Dextre does
- 1
A fixed chain with a gate at every stage
Requirements, design, coding, testing and deployment always run in that order. Nothing moves forward until a person approves it.
See it in the example job ↑ - 2
Feedback, not restarts
Decline a stage and the work returns to the same agent with your comments, so you refine it instead of starting again.
Try a decline ↑ - 3
Agents with only the tools they need
See a blocked action ↑ - 4
A full record of what happened
See the record ↑ - 5
Test results you can trust
See the runner decide ↑ - 6
Your choice of AI model, with spend limits
See the caps ↑ - 7
Works with your code and boards
Dextre works with Azure Repos and GitHub, delivers changes as pull requests for your team to review, and traces work to Azure DevOps boards.
- 8
Sign-in and roles
Sign in with Microsoft Entra ID. Roles decide who can start a job, approve a stage or take a change live, and only an administrator can approve go-live.
Integrators sell hours. Dextre changes what the hours buy.
Most delivery effort goes into drafting: requirements, specifications, configuration records, test cases, runbooks.
Dextre takes the drafting. Our consultants and engineers keep the judgement, and your budget stops paying senior rates for transcription.
AIM is moving past the traditional SI model, with AI working alongside every one of our people.
Decided by people
- Scope decisions
- Architecture
- Sign-off and go-live
Drafted by Dextre, checked by people
- Requirements documents
- Design specifications
- Configuration records
- Test cases
- Code scaffolding
- Training material
- Cutover runbooks
Same people, same accountability. Their hours move to scope, architecture, review and sign-off.
Custom software, built without a blank page.
Web applications, portals, APIs and custom agents. Dextre drafts the stories, scaffolding, tests and documentation. AIM engineers own the architecture and every merge.
What Dextre drafts. What engineers own.
Dextre drafts
- User stories and acceptance criteria
- Code scaffolding and integration mappings
- Unit tests, including edge and negative cases
- First-pass code review against standards
- Technical documentation, kept current
AIM engineers own
- Architecture and extension patterns
- Security and performance review
- Final code review and every merge
- Release authorization with your product owner
Where Dextre works, stage by stage.
Discovery
Question sets for each process area, workshop agendas, and workshop notes structured into decisions, risks and open questions.
Running the session, reading the room, and deciding what is out of scope.
Requirements
Requirement statements and acceptance criteria from approved workshop output, with traceability maintained as scope changes.
Approving requirements, and resolving conflicts between departments.
Custom agents, built around how your business works.
Dextre builds AI agents for one job in your business, on your data and your security model. Each has a named owner, scoped access and an approval step. AIM builds them, governs them and keeps them improving.
Example custom agents · illustrative, not packaged productsRequestInvoice 4471 does not match its purchase order.
- planIdentify the mismatch: quantity received is short by two units.
- retrievePull the purchase order, goods receipt and vendor terms.
- draftDraft a short-payment note and a vendor query.
- approveAbove the agent limit, so the AP lead decides.
- actPost the short payment and send the query.
- logEvery action recorded for audit and evaluation.
RequestStart the October close checklist.
- planBuild the checklist from last month and this month’s calendar.
- retrieveCheck which reconciliations and accruals are still open.
- draftDraft reminders to each owner with the item and the deadline.
- approveThe controller reviews the list before anything is sent.
- actSend reminders and track completion.
- logStatus and exceptions reported to the controller daily.
RequestExpense claim from a sales manager, travel to Calgary.
- planCheck each line against the travel policy.
- retrievePull the policy, the receipts and the trip approval.
- draftFlag a hotel night above the policy rate, with the clause.
- approveThe approving manager accepts or rejects the flag.
- actRoute the claim for payment with the decision attached.
- logDecision and policy clause stored with the claim.
RequestNew hire: analyst, starts Monday, Toronto office.
- planList the role’s accounts, equipment, training and documents.
- retrievePull the role template, the manager and the start date.
- draftDraft the welcome pack, IT requests and first-week schedule.
- approveHR confirms the pack and the access requests.
- actSubmit requests and send the welcome pack.
- logProgress visible to HR and the hiring manager.
RequestHow many days can I carry over into next year?
- planClassify the question: vacation carry-over.
- retrieveSearch the approved policy library for this employee’s province.
- draftDraft an answer that cites the policy clause.
- approveNo record changes, so no approval needed. Unclear cases go to HR.
- actReply to the employee with the source attached.
- logQuestions with no clear answer are flagged to HR as policy gaps.
RequestFive days of vacation in December.
- planCheck the dates against team coverage rules.
- retrievePull the balance and the team calendar.
- draftDraft the request with balance and coverage notes.
- approveThe manager approves or declines.
- actUpdate the calendar and the balance.
- logDecision recorded in the HR system.
From one repeated task to a governed agent.
- 01 · You
Name the job
One task your team repeats, the systems it touches, and who owns the outcome.
- 02 · Dextre
Drafts the agent
Agent specification, grounding sources, permissions and an evaluation set, drafted from your process.
- 03 · AIM
Builds and tests
AIM engineers build the agent, run it against the evaluation set and fix what fails.
- 04 · Your owner
Approves go-live
The business owner signs off before the agent touches real work, and reviews it after.
First-party Dextre agents are coming.
Pre-built agents for common work in four functions. Until they ship, AIM builds what you need as a custom agent.
- Coming soonFinanceRoadmap
- Coming soonHRRoadmap
- Coming soonSalesRoadmap
- Coming soonMarketingRoadmap
The controls that let agent two go live faster than agent one.
- Inventory
Every agent listed
Each agent is registered, described and reviewable from the day it is created.
- Owner
A named business owner
Someone in the business is accountable for what the agent does and when it retires.
- Access
Your security model
Agents see only what the requesting user may see. Access follows your rules, not the agent’s convenience.
- Approval
People approve changes
Actions that change records carry an approval step until the business decides otherwise.
After go-live
Dextre is extending into the managed services AIM runs once your platform is live.
In developmentFrequently asked questions
Does Dextre replace developers?
No. Agents work in an isolated workspace, and a person approves every stage and decides what is merged or released.
Does Dextre replace your consultants?
No. It changes what they spend time on. Drafting moves to Dextre. Scoping, architecture, review and sign-off stay with named people.
Does Dextre release to production on its own?
No. Nothing goes live until a person approves it, and only an administrator can approve go-live.
Can we see what it did and why?
Yes. Every tool call, blocked action and human decision is recorded, along with the test output that decided the quality verdict.
What if we disagree with a stage?
Decline it. The work returns to the same agent with your comments attached.
Which AI models does it use?
Your organization chooses from the models it approves, and can pick one for each stage.
Legacy ERP Modernization Discovery
A paid, fixed-scope discovery of what your legacy ERP estate contains before you replace it. Two to three weeks, Dextre-assisted, human-governed.
AI delivery with a human gate after every stage.
Dextre is a governed AI software delivery platform from Architecture in Motion Inc.
Request a demo →