Point it at the deal folder. Get the tower back.
TermsDesk reads a submission folder or a forwarded thread and returns a structured placement — layers, carriers, limits, attachment points, premiums, effective dates, quote status. Nobody types it in.
For wholesale brokers, MGA underwriting staff, and the ops people keeping forty E&S placements straight at once.
Four ways a placement goes sideways, none of them exotic.
Excess and surplus lines has no standard form, no standard submission, and no AMS that speaks tower. What it has is Outlook, a shared drive, and a spreadsheet somebody maintains by hand.
The tower lives in three places
Attachment points in a draft Word schedule, limits in a signed PDF, revised excess terms in message eight of an eleven-message chain. No single view shows the tower as it currently stands.
Version three of the SOV
A corrected statement of values goes out; the superseded file is still attached to an older thread. Two carriers quote off two different TIVs and nobody notices until the binder.
The supplemental nobody chased
A carrier asks for sprinkler and COPE detail before it will firm up terms. The request sits in a sent folder. The quote ages out six days before the effective date.
Sixty days, then all at once
Retail agent, wholesale broker, carrier, and insured, over a two-month lead time. Nothing is urgent for six weeks, and then three deadlines land in the same afternoon.
Sixty seconds, folder to tower.
Walk it yourself. This is the Rincon Cold Storage folder — a shared-drive directory and one forwarded thread — resolving into a placement you can work.
This is the input, unedited: no naming convention, three versions of the SOV, terms buried in a reply chain, and one supplemental that never came back. TermsDesk expects this rather than asking you to clean it up first.
Forward the thread to a deal address, or connect the shared drive folder. Both produce the same structured placement.
Revised terms sitting in message eight of eleven get read like any attachment, including the ones quoted inside a reply.
Nothing binds, sends, or signs itself. Extraction is a first draft of the deal, presented for your correction.
One card, and you know where the placement stands.
Hover a note to see what a broker is actually reading. Nothing here is decoration — every element answers a question you'd otherwise ask three people.
DL-2026-0418 · Property · CA. One id the retail agent, the underwriter, and your accounting team can all quote back to you.
The card reads QUOTED because layer 3 is quoted, even though two layers are bound. A tower is not placed until every layer is.
Seventeen days to bind, not seventeen days since submission. The only clock that matters runs backwards from 04/17.
The $3M excess layer is most of the tower and it is the layer still unbound. At a glance you know which conversation is load-bearing.
7.60 / 3.46 / 1.55%. Descending rates as you go up the tower is the sanity check; a layer priced out of line shows up here first.
An overdue supplemental on the unbound layer, flagged as blocking. Not a task in a list — a condition on the deal.
Five states, readable at a glance across forty rows.
Colour is never the only signal. Every state carries a glyph and a border, so status survives a bad monitor, a printout, and colour blindness.
Out to market, nothing back yet. The carrier has the submission and the clock is running.
Terms in hand and not bound. Usually still carrying subject-to items and a validity date of its own.
Coverage in force for that layer, binder issued. The only state that closes a hole in the tower.
Carrier is out. The layer needs a different market, and the tower has a gap until it finds one.
A quote aged past its own validity window. Functionally no quote — and the easiest state to misread as one.
Expired and declined are the pair that costs money. A declined layer needs a new market; an expired quote needs the same market to re-issue. Mistake one for the other on a Thursday and you are explaining a gap in the tower on Friday — so the two never share a hue, a glyph, or a border in TermsDesk.
Sixty-day lead times are how things fall through.
A submission goes out in February for an April 17th effective date. Nothing feels urgent for six weeks, and then three things are urgent at once: a supplemental the carrier asked for in March, a quote that lapses on its own terms, and a bind order nobody sent.
TermsDesk reads the dates out of the documents themselves — effective dates, quote validity windows, subjectivity deadlines — and counts down from them. You are not maintaining a reminder list; you are looking at one that maintains itself.
Quote valid until 04/11 means the countdown starts at 04/11, whether or not anyone noticed.
Two days late reads as two days late — not as a task sitting quietly in a list.
You are handing us client submissions. Here is exactly what happens to them.
Written plainly, because "enterprise-grade security" is not an answer you can give a retail agent who asks where their insured's loss runs went.
One region, one database, your tenant
Deal data and documents sit in a single US region on AWS, in a database partitioned per brokerage. Encrypted at rest with AES-256 and in transit with TLS 1.3. Nothing is copied to a second cloud for processing.
Your team, at deal level
Access is granted per deal, not per account, so a producer sees the placements they are on and nothing else. Every document view and export is logged with a name and a timestamp you can read.
We cannot read your deals by default
Amasiko staff have no standing access to your documents. Support access is something you grant, scoped to one deal, expiring in 24 hours, and recorded in your own audit log. No exceptions for demos or debugging.
Your submissions do not train anything
Documents are processed to extract your deal and are never used to train shared or third-party models. Extraction runs against providers under a zero-retention agreement, and the subprocessor list is available on request.
Export and deletion on your say-so
Full export of deals and original files at any time, in the formats you put in. On written request the account and its documents are deleted within 30 days, backups included, with written confirmation.
We are pre-launch and we do not hold a SOC 2 report yet, so we do not imply otherwise on a marketing page. What we can send you today is the controls document, the subprocessor list, and a call with the person who wrote both.
Bring us one messy placement.
Send a folder or forward a thread from a deal you have already closed, so nothing is at risk. We will run TermsDesk against it on a call and you can tell us where it is wrong. That is the whole pitch.
Amasiko Systems LLC
A small software company building one product for one segment. TermsDesk is not a platform, a marketplace, or an AMS replacement — it is deal organization for wholesale E&S, and that is the entire roadmap.