Stop underquoting
AWS engagements.
TNA Pro turns a discovery call into a defensible scope and a day count — the same way, every time, by whoever runs it.
The problem it solves
A scope is a number
somebody has to defend.
Usually months later, in a room where the project is over budget and nobody can reconstruct how the estimate was reached. In our own delivery we have seen two architects scope the same customer and come back with day counts around a third apart. Neither was careless. They had no shared instrument.
How it works
Four stages, in order, because scoping is a procedure.
Frame the engagement
Customer, industry, engagement type. Pick a type and its scope template loads with it: a migration and a landing zone start from different pages.
Select the technical scope
95 AWS services with milestones, steps and complexity bands behind each one. Days and price recalculate as you select, so the commercial consequence of a choice is visible while you are making it.
Record what you don't know
Open questions and blockers are first-class, flagged and counted. An unknown that is written down becomes a caveat in the SoW; one that is not becomes a change request.
Export the analysis
One row per milestone — service, phase, responsibility, days and steps — ready to drop into the statement-of-work template and the tracker your firm already uses.
What comes out
Every number traces back to a decision.
A day count on its own is a guess with a decimal point. TNA Pro keeps the service, the complexity band and the milestone breakdown behind every figure, so when someone asks where it came from six months later, there is an answer.
A row per milestone
Service, phase, whose responsibility, billable days, and the steps behind them — the analysis rather than a document. Your SoW template is already right for your firm; we are not going to redesign it.
The open questions
Every unknown flagged during the call, carried through as a caveat — rather than discovered months later as a change request.
Numbers that reconcile
The exported rows add up to the quoted day count exactly, so the plan you deliver against cannot drift from the number you sold.
Built for AWS partners
It already knows the catalogue.
TNA Pro is Digital Umbrella's first product. The company builds operational software for delivery businesses generally; this one happens to be for AWS partners.
TNA Pro was built inside ZynoStack, a Cairo-based AWS consulting partner, for its own delivery team — and used on real engagements before it became a product. The service catalogue, the complexity bands and the day-rate model all came out of that work.
- Buy through AWS Marketplace against existing commitment — no new vendor onboarding
- Your currency, tax rate and tax treatment are all configurable
- Tenant isolation enforced at the storage key itself
- Runs entirely on AWS, from one auditable CloudFormation template
- Every scope kept, so an estimate can be reconstructed months later
Pricing
Priced per delivery team, not per seat.
Charging per seat would penalise the behaviour the tool exists to encourage — putting the whole delivery team in the same instrument. We are still setting the number. It will be published in full on the AWS Marketplace listing rather than kept behind a conversation.