Clear answers about the product direction

No. It is designed around governed knowledge, complex RFP requirements, proposal workflows and professional accountability.

No. Your team writes, edits and approves all content. ProposalOS provides the structure: requirements, evidence, review workflow and readiness checks.

Professional-services teams handling frequent, complex and collaborative formal proposals gain the clearest value — typically 20–99 employees preparing at least ten formal proposals a year with three to ten contributors on each.

Documents remain evidence. Reusable knowledge carries source locations, ownership, versions, approval and quality cues.

It marks the gap instead of filling it. Unsupported claims, missing responses and unmapped requirements are raised as items for a person to resolve — the assistant never presents a claim it cannot trace to an approved source.

No. Customer content is not used for shared external-model training by default. Each organization's documents, knowledge, search and AI context are kept separate from every other organization's.

No. Submission, approval and sign-off are human actions. Export is gated on unresolved mandatory items, but the decision to submit always belongs to an authorized person in your organization.

Data is stored per organization with role-based access, and administrative access is controlled and recorded. Hosting region, retention periods and any sub-processors are confirmed in writing during onboarding rather than assumed.

Yes. Access follows roles — organization administrator, proposal manager, knowledge manager, contributor, reviewer and executive viewer — so contributors see the sections they are assigned and approvers see what they must decide on.

This is product direction rather than a capability you can use today. The intended behaviour is bilingual interfaces with full right-to-left layout, mixed-direction content inside a single document, and review state attached to the section rather than to one language's copy of it — so an approval given in Arabic is the same approval seen in English. Ask us where it stands before it forms part of a decision.

Yes — export targets Microsoft Word using your organization's template, structure and branding, so the submitted document looks like your document rather than the tool's.

Onboarding is a guided process: connect or upload an initial document set, review what was extracted, approve the knowledge worth reusing, then run a first live tender. Timelines depend on how much archive you bring, and are agreed before the pilot starts.

No, and it is usually a mistake to try. Start with the material a live tender actually needs — company facts, recent references, current methodologies and valid certifications — and let the repository grow from real use.

It shows the product's screens and workflow using deterministic sample data. The assisted steps in it are clearly labelled simulations backed by local fixtures — no external AI service is called — so what you see is the experience and the controls, not a live model's output.