IT · App Starter
A working asset tracker — check-out ledger, license seats, depreciation, audits — generated into a codebase you own.
Describe how your organization hands out hardware, and Dual7 generates this asset system around it: six connected entities, a check-in/check-out ledger, and an audit trail, shipped as a real full-stack app. Add a field, change a workflow, integrate your directory — it's your code, not another agent to license per node.
01 · Data model
Asset tracking fails in the gaps between spreadsheets — the laptop that left with a contractor, the license renewed for a team that shrank. Six connected entities close those gaps, and everything below reads from them.
| table | what it holds |
|---|---|
assets | Serialized hardware — laptops, monitors, phones — with model, purchase cost and date, warranty, current holder, and lifecycle status. |
licenses | Software entitlements with seat counts, keys, renewal dates, and per-seat assignments to people or machines. |
accessories | Quantity-tracked stock — chargers, docks, cables, adapters — drawn down at handout without pretending every cable has a serial. |
checkouts | The ledger itself: who took what, when it went out, when it's due back, and the state it returned in. |
audits | Scheduled verification passes with per-asset scan results, so 'the records match reality' is a dated fact rather than a hope. |
locations | Offices, storage rooms, and remote — every asset and accessory pool has a place it belongs, and drift shows up in reports. |
02 · Screens
Every handout and return is a ledger entry against a person and an asset, with condition captured both ways. Offboarding stops being an email thread: one screen lists everything an employee holds, and clearing it is checking items back in.
Seats assigned versus seats purchased, per license, with renewal dates on a timeline. The unused-seat report before each renewal is the module's whole argument — most teams find the savings in the first month.
Purchase cost and date drive straight-line depreciation per asset, and lifecycle status — deployed, in storage, in repair, retired — keeps the book honest. Finance gets a defensible number without a second spreadsheet.
Every status change, assignment, and edit is recorded with who and when. When an asset goes missing or a compliance review lands, you replay history instead of reconstructing it from memory and inbox search.
03 · Process
Tell Dual7 what you track, who hands it out, and what your lifecycle looks like — purchase to deploy to retire. Plain language is enough; the starter supplies the structure.
Get the working tracker in minutes, then tune it conversationally: add a warranty-expiry report, a custom asset type, an approval step on high-value checkouts. Every change lands in code you can read.
When IT is ready to run on it, promote it through Dual7's approval gates to production — audit trail included, deployed on your infrastructure, records in your database.
04 · Fit
The sheet was accurate the day it was made. A ledger with enforced check-in/check-out stays accurate because handing out a laptop and recording it are the same act — not two acts where the second one gets skipped on busy days.
Insurance renewals, SOC 2 evidence requests, and grant reporting all ask the same question: what do you own and where is it? Scheduled audits with per-asset scans turn that from a two-week scramble into a report you already have.
Asset-management SaaS often prices by tracked item, which quietly punishes you for keeping good records. Owning the codebase removes the meter: track every cable if it's useful, and the bill doesn't move.
Generate a tracker per client — their asset types, their locations, their branding — instead of cramming every client into one multi-tenant tool. Each deployment is a codebase the client could even take over someday, which is a selling point, not a risk.
05 · Yours
Start by making the vocabulary yours: rename asset types, add the fields your workflow actually keys on — PO number, cost center, assigned project — and the screens and reports follow. In Vibe mode these are conversational edits that land as schema and code changes you can review.
Bigger moves are normal engineering on a normal codebase: sync people from your identity provider so checkouts assign to real directory users, add a self-service request queue in front of the ledger, or wire barcode or QR scanning into audits with a phone camera. The generated app has no runtime dependency on Dual7.
Most asset tools rent you a database you feed and can't take with you — priced per asset, per user, or per agent installed. This starter generates the schema, the ledger, and the reports as source code in your repository, running on your infrastructure. The record of what your company owns seems like a strange thing to lease.
The trade-off is real: you operate the app. Dual7's governed pipeline is built for exactly that — approval gates before changes hit production, a full audit trail, and regeneration when the structure needs to change rather than accrete patches.
06 · Industries
An asset system built for 1:1 programs — student assignments, loaner pools, carts, damage fees — generated into code your district owns.
An asset system built for clinical equipment — PM schedules, recall response, department custody — generated into code you own.
A working full-stack tracker generated into a codebase you own: six connected entities (assets, licenses, accessories, checkouts, audits, locations), a check-in/check-out ledger, license seat tracking, straight-line depreciation, and a complete audit trail. Your data lives in your database on your infrastructure.
Yes — licenses carry seat counts, keys, and renewal dates, with seats assigned to people or machines. The seats-purchased-versus-assigned view surfaces shelfware before the renewal invoice does.
The schema is scan-ready — every asset has a unique tag field — and adding camera-based scanning to checkouts and audits is a normal extension in Vibe mode. Because it's your code, you can match whatever label format your existing tags use.
One screen lists everything a person holds — assets, accessories, license seats — and clearing them is checking each item back in, with condition recorded. The ledger entry is the evidence, which is what HR and security actually want from the process.
Purchase cost, date, and useful life drive straight-line depreciation per asset, rolled up by category and location. If your finance team uses a different method, the calculation is a readable function in your codebase, not a vendor setting.
No — this is a records system, not endpoint monitoring. It tracks ownership, location, and lifecycle. If you later want automated hardware facts, you can integrate a discovery source and write into the same assets table the screens already read.
Dual7 App Starters
A working asset tracker — check-out ledger, license seats, depreciation, audits — generated into a codebase you own. Describe your version to start — the output is a project you own.