How the product works, task by task
Product documentation organized by what you are trying to do, from connecting a source to exporting a submission package.
The work runs in one direction — sources produce opportunities, opportunities are qualified, qualified ones become responses, responses are delivered and their outcomes recorded. This is that path in order, with what each step needs before it will do anything useful.
The first week, in order
Complete the company profile
Matching has nothing to score against until this exists. It holds what the firm sells, where it works, its certifications and set-aside eligibility, and its past performance record. A profile left at defaults produces matches that look random, because they are.
Choose the sources that apply to you
Federal, state, local and public authority sources are read continuously. Selecting the jurisdictions and categories you actually sell into is what keeps the feed to a size a person can read.
Save a search, then let it run
A saved search is a standing question. It back-fills against what is already published so you can see whether it is asking the right thing, then notifies on new records that match.
Invite the people who will review, not just write
Review and approval gates need somebody to hold them. A workspace where one person holds every role is a workspace where the approval step is a formality.
Upload one past proposal
The content library indexes what a firm has already written. One real response is worth more at this stage than a week of writing boilerplate, because it is what section drafting retrieves from.
Matching quality is downstream of the profile
Finding opportunities
Search and saved searches
The search URL is the query — filters live in the address bar, so a search can be bookmarked, shared with a colleague, or sent in an email and open the same result set.
Why a match scored what it did
Every score shows its contributions: capability overlap, geography, past performance, set-aside eligibility. A score with no explanation is a number nobody can act on.
Signals, before anything is published
Budget line items, board approvals and expiring contracts, each carrying its source. Signals are evidence that a purchase may be coming — never a confirmed opportunity, and the interface says so.
Recompetes
Contracts approaching expiry with option years accounted for, each with an explicit confidence and the award history behind it.
Deciding what to bid
A solicitation package is uploaded or pulled in from its source, read, and reduced to two lists: the requirements, and the criteria the response will be evaluated against. Every extracted item cites the page of the document it came from, so a disputed requirement is settled by clicking through to the source rather than by re-reading the package.
The Go/No-Go decision is recorded against the opportunity — the verdict, the reasoning, and who made it. That record is what makes a later debrief useful, and it is the reason a firm can tell the difference between an opportunity it declined and one it missed.
A requirement extraction is a draft, not a verdict
Extraction is reliable on well-structured packages and less so on scanned documents and drawings. Items can be added, edited and removed, and nothing is deleted — the original extraction stays attached.
Mandatory items are separated from evaluated ones
The two carry different consequences and belong in different parts of the plan. Mandatory failures end the bid; evaluated items are where writing time earns its keep.
Amendments are tracked against the original
When a package is amended, the changed requirements are shown as changes rather than replacing the list silently. A requirement that moved is the one most likely to be missed.
Building the response
Plan the outline
The outline is derived from the solicitation itself. Where the buyer prescribes a structure, the buyer wins over any house template — that precedence is enforced rather than left to the writer to remember.
Draft section by section
Each section is drafted with a prompt shaped by what that section is for, the requirements mapped to it, and what your library already contains. Drafting one section does not silently rewrite its neighbours.
Edit against the page limit
Length is measured against the buyer’s constraint while you write, not discovered during assembly. A projected page count is shown as sections change.
Move it through review
Sections carry state — drafting, in review, approved — and a version history that shows who changed what. Regenerating a section never discards an edit made by a person.
Check compliance before assembling
The requirement mapping shows what is answered, what is partially answered and what is not answered at all. Three ways of being absent, which are not the same problem.
Generated text is a draft that has to be read
Delivering and recording the outcome
A finished response leaves as one of two things: a branded link, or a file. The link can carry a password, an expiry and the recipient’s name as a watermark, and it can be withdrawn after it has been sent. The file is a PDF laid out by code at whatever page size the buyer’s instructions assume.
Once it is submitted, the submission is tracked as its own record — submitted, then won, lost or withdrawn — and that outcome is what the analytics read. Win rate by agency, by contract type and by evaluation criterion is only as good as the outcomes recorded against it, which is why the record is a separate step rather than an inference.
Delivery and exports
Branded links with password, expiry, watermark and revocation, or a PDF at any page size.
Analytics
Pipeline, win rate and where responses lose — read from recorded outcomes rather than guessed.
Workspace, seats and plan limits
What a plan limits
Seats, company profiles, active pursuits, AI generation, document processing and exports each carry an allowance. Current usage against each is shown in the workspace, and the limits themselves are on the pricing page, read from the billing catalog rather than typed anywhere.
What happens at a limit
Some allowances warn and keep working; others refuse the action and name the limit and the plan that raises it. Which is which is deliberate, and the message says which one you have hit.
Agency workspaces
An agency can hold client workspaces that keep their own profiles, content and pursuits while billing to the parent. Client data does not cross between them.
Signing in
Email and password, or Google. Sessions are per-device and can be ended individually from the account settings.
When this does not answer it
Send the workspace name, what you were doing and what happened instead. Where the product refused an action, quote the message — the errors name the limit or the permission involved, and that sentence usually identifies the cause without any further investigation.
Contact the team
Questions about the product, an account, a bill, or a security concern.
How data is handled
Tenant isolation, encryption, access control, retention and how to report a vulnerability.
Common questions
- Why are my matches poor?
Almost always because the company profile is thin. Matching scores against capabilities, geography, past performance and set-aside eligibility, and each match shows which of those produced its score — start from the contributions on a match that looks wrong.
- Can I edit a requirement the product extracted incorrectly?
Yes. Requirements can be added, edited and removed, and the original extraction stays attached with its page citation, so a later reader can see what the document said and what was changed.
- Does regenerating a section discard my edits?
No. A regenerated draft and a person’s edit are held separately, and the version history shows both. Regeneration is safe to press twice.
- Can a sent proposal be withdrawn?
A delivery link can be revoked, and revocation takes effect immediately. A PDF that has been downloaded cannot be recalled, which is the argument for sending the link.
- What happens when a plan allowance runs out?
It depends on the allowance. Some warn and continue; others refuse the action outright and name both the limit reached and the plan that raises it. The message tells you which case you are in.
- Is there an API?
Not yet. API access is listed on three plans and the surface is not built; the API documentation page sets out the current status and the design that has been decided.
Related
Sales, support and everything else.
Endpoints, authentication and webhooks.
Plan the outline, draft each section, compose the document.
How customer data is isolated, encrypted and retained.
See what you are not bidding on.
Connect a source, describe what your company does, and look at the opportunities that come back before deciding whether any of this is worth your time.