PursuitBasisPursuitBasis software · In development
Give every next step a clear basis.
Our early development includes AI-assisted document review. The broader product is being built to connect commitments, source records and follow-through, with review and action governed by the customer’s workflow and permissions.
How we’re approaching the product
See what changed and what needs attention.
Start with the source record. Show the specific issue and why it matters. Keep earlier versions, unresolved questions and the next responsible person in view.
This prepared supplier example illustrates the approach.
Four routers need clarification.
Quote and award comparison
The award lists four fewer routers than the quote. The quantity needs to be reconciled before a purchase is authorized.
View the example records
Quote Q-024 lists 24 routers and 24 separate support entitlements.
Award A-020 lists 20 routers and 24 support entitlements, leaving a difference of four routers.
These records and the comparison were prepared for this example. The page does not analyze or approve them.
Resolve the difference and keep the remaining work visible.
View the corrected example award
24 routers. 24 support entitlements.
The corrected award matches the quoted quantities. In this example, that resolves the four-router difference.
Delivery receipts, support-entitlement evidence, acceptance and financial review still need their own records. Viewing the correction creates no purchase, invoice or payment.
Follow the supplier exampleDevelopment status
What you can explore today.
PursuitBasis is in development. This website presents the product direction and prepared examples; it does not provide access to an operational platform.
- Preview
- Browse the lifecycle, open example records and follow two fictional workflows.
- Demonstrations
- The service and supplier examples use prepared records and findings. They do not analyze documents, save business records, approve work, place orders or process invoices or payments.
- Product development
- Early development includes private AI-assisted review tests using public solicitation documents. The connected platform, supported live integrations and customer deployment remain in development. Those tests do not establish production readiness or measured customer results.
- Availability
- The broader software is still being developed. Availability, pricing and any implementation or support scope will be confirmed before an engagement.
Two example workflows
See how the work connects.
Harbor Field Services and Meridian Federal Supply illustrate the product direction. These are fictional examples, not customer case studies.
From service report to accepted work.
Harbor Field Services follows a scope change through a missing attachment, corrected evidence and separate acceptance records.
View the service example02 / Supplier and resellerFrom quote to delivery evidence.
Meridian Federal Supply follows a quantity difference through award correction, partial deliveries and support entitlements.
View the supplier exampleStart a conversation
Where does the handoff get difficult?
Describe the work, the tools involved and what a useful result would look like. A general description is enough to begin.
Start an inquiryEmail inquiry only. Review and send in your email app.