JIRAintake
Jira ticket DS-6 lands
ticket · intake
Demos · costed Jira ticket · dispatch reel
Costed Jira tickets?
One work item through the software factory, start to finish. A Jira ticket went in. AI developers and testers built and tested it. Here's what it cost.
This Java backend ticket cost ≈ $27 to develop & QA with awks (agentic workers).
Initiative costing is no longer a vague FTE estimate.
This ticket cost ≈ $27 to build and QA
How?
▶tap to expandAwkTeams.
Automated Delivery Pipeline
▶tap to view the machineryHandoff → dev → QA
screenshot · click to open
OG(dev)First pass
screenshotQAFirst pass
▶
screenshotHandback ← QA → dev
screenshot · click to open
$27settled · end of reel
DS-6 cost precisely 2,660 credits (≈ $27)
▶Slack receiptpress ▶ play to reveal
jira → uat preview· paid in credits ·
The payoff
What does this mean for my business?
Ticket in, evidence out — you approve what matters
A delivery pipeline run by a team of AI agents (awks). Write the Jira ticket. Get back a reviewed change, a preview URL, and what the ticket cost.
Cost you can see
Credits are metered per ticket — every ticket carries a real, itemised price in credits, so engineering spend is a line item you control, not a guess.
Managed tokenomics
We manage token spend for you: each task is routed to a model matched to its complexity, and context is kept lean as work runs — so credits go to the work, not to overhead.
Proof by default
Each change leaves a shareable trail — DoD evidence, QA results, code review, handoff briefs — ready for sign-off.
The reel · 09 stationsClick to enlarge · screenshot & video
01Jira · intake
Jira ticket · requirements
→
02Slack · pickup
Picked up in Slack
→
03Dev · DoD
Build + DoD evidence
→
04Handoff · dev → QA
OG (dev) → QA handoff brief
05QA · evidence
QA test evidence
→
06Handback · QA → OG
QA → OG handback brief
→
07Iterate · fix & re-verify
Fix & re-verify loop
→
08Preview · shareable URL
Preview URL surfaced
09Ticket · settled
2,660cr≈ $27
End of reelKey artifacts · shareable proof
What the reel leaves behind.
A1Google Doc
Definition-of-Done evidence doc
Live-updated doc the OG mirrors during the build — screenshots, invariants, notes. Shareable link posted in-thread.
A2Canvas
Code review
Findings surfaced on the diff: correctness, simplification, efficiency. Each finding links back to a Jira sub-task.
A3Canvas
Handoff brief
Every handoff — dev→QA, QA→dev, dev→UAT — writes a brief canvas: what changed, what to verify, what still hurts.
The takeaway · the question every AI bill leaves unanswered
What did the tokens buy? Metered per work item.
What went in
2,660
credits
≈ $27
One Jira ticket, all-in
Every agent on the thread, counted once
Every agent on the thread, counted once
DS-6 · Backend API - Java
A seat bill tells you who spent it.
It cannot tell you this.
What came out
- A reviewed change2 review rounds · verdict clean
- A Definition of Done, with evidence16 / 16 items verified
- A QA suite, authored and run21 cases, round 1
- A real failure, caught20 / 21 passed · 1 handed back
- Fixed, then re-verified24 / 24 passed
- Handoff and handback briefsOn the ticket, dev → QA → dev
- A preview URL and a moved ticketSign-in gated · ready for UAT
Same spend. The difference is that it is sorted by the work it produced, not by the user seat it was billed to.
Cost → value
Itemised.
Every figure above is from the DS-6 thread and its artefacts on this page · credits at $0.01 · one ticket, not a price list