From a sixty-page RFP to a costed proposal you can defend.
Proposal Engineer reads the tender, pulls out every requirement, flags what is missing or contradictory, and carries the bid through solution, scope, estimate and price to a proposal and SOW. You approve every line, and every line shows its source.
- No card, no sales call
- Set up within a working day
- Data hosted in Frankfurt, EU
| Ref | Requirement | Category | Priority | Confidence |
|---|---|---|---|---|
| R-004 | Replace edge switching at every branch site with 802.1X port authentication …all branch edge switches shall support 802.1X port-based authentication… | Technical | High | High |
| R-007 | Cutover work confined to Sunday 00:00–06:00 maintenance windows …no service-affecting work may occur during trading hours… | Operational | High | High |
| R-011 | Sustain 99.95% availability measured per site, per calendar month …availability of 99.95% measured at each site… | Non-functional | High | Medium |
| R-015 | Hand over as-built documentation before acceptance sign-off …as-built documentation shall be delivered prior to acceptance… | Commercial | Medium | High |
What the document does not say
- CriticalHow many branch sites are in scope?The document says “all branches” four times and never counts them. Every hour in this bid is a multiple of that number.
- Critical99.9% or 99.95%?Section 3 and section 5 disagree. One of the two carries service credits.
- ImportantNo hardware inventory, no cutover dateNeither the existing estate nor the required completion date appears anywhere in the pack.
EU data residency
Documents and data stored in Frankfurt (eu-central-1)
Isolated in the database
Row-level security keeps each company's data apart
Every AI run on record
Model, prompt version and outcome logged for audit
A person approves
Nothing reaches a customer without human sign-off
Measured, not promised
- of processing from RFP upload to a costed proposal and SOW
- ~14 minof processing from RFP upload to a costed proposal and SOW
- stages, each accepted by a person before the next begins
- 11stages, each accepted by a person before the next begins
- prices calculated by the AI model — the application does the arithmetic
- 0prices calculated by the AI model — the application does the arithmetic
Processing time measured on the live service in September 2026, on a synthetic telecom RFP with 11 requirements. Your review time comes on top, and larger tenders take longer.
Why the first hours matter
The expensive mistakes happen before anyone writes a word
Found in delivery
A requirement gets missed
Clause 7.4.2 said the migration had to happen outside trading hours. Nobody priced night shifts.
Found in the margin
An assumption goes unasked
“Approximately 200 branches” became 200 in the model. It was 260. The margin was gone before kick-off.
Found after signature
The document contradicts itself
Availability is 99.9% in section 3 and 99.95% in section 5. One of those carries service credits.
How it works
From tender pack to an approved price, in three steps
- 1
Upload the RFP and its annexes
Tender document, appendices, clarification emails — PDF, Word, text or CSV, up to 25 MB each. It reads them in full; it does not skim.
- 2
Get the document taken apart
Requirements, conditions, deadlines, service levels and evaluation criteria, each on its own line and quoted from the source — plus what the document leaves unsaid, and where it contradicts itself.
- 3
Carry it through to a price
Solution, scope, assumptions, risks, effort, cost and margin — then the proposal and SOW in Word and PDF. Nothing moves to the next stage until you accept it.
The chain, stage by stage
- RFP
- Requirements
- Missing information
- Solution
- Scope
- Assumptions & risks
- Estimate
- Price
- Proposal & SOW
- Review
- Approval
What it does
Everything between the tender and the signature
One workspace for the whole bid. Each stage builds on the one before, and each one is yours to accept, edit or reject.
Takes the RFP apart
Requirements, conditions, deadlines, service levels and evaluation criteria — each on its own line, with the sentence it came from.
Finds what is missing
Open questions ranked by what they block, and every place the document contradicts itself, ready to send as clarifications.
Designs the answer
Solution, scope, assumptions and a risk register, drafted against the accepted requirements and your own past proposals.
Estimates the effort
A work breakdown with hours by role, priced against your rate cards, alongside what comparable bids were estimated at.
Prices it exactly
Cost, contingency, margin and discount calculated by the application — and approved by a person before anything is sent.
Writes the documents
Proposal and SOW in Word and PDF, in English or Turkish, versioned, with a review of coverage and consistency before you send.
Deterministic pricing
The model suggests. The application calculates.
A language model is good at reading a tender and unreliable at arithmetic. So every number that reaches a customer — hours × rate, cost, margin, discount, price — is computed by code you can check, and nothing is final until someone approves it.
- Margin and markup shown side by side, so the two are never confused
- Change a term after approval and the approval lapses until it is signed off again
- Every figure traces back to an hour on the estimate and a rate on your card
- Labour · 2,834 h
- €194,060.00
- Travel
- €1,200.00
- Direct cost
- €195,260.00
- Contingency (10%)
- €19,526.00
- Internal cost
- €214,786.00
- Margin (35% of price)
- €115,654.00
- Customer price
- €330,440.00
The difference
You are going to put your name on this. So you can check its work.
Most proposal tools ask you to trust an answer. A presales engineer signing a technical response cannot afford to, so this one works the other way round.
Every line shows its source
Every requirement carries the exact sentence it was read from, so you check it against the customer’s own words rather than a summary. A tool that cannot show you its source is asking you to sign for its guess.
It never decides anything
AI proposes; you accept, edit or reject. Re-running a stage never overwrites a line you have already reviewed, so you can press the button twice without losing an afternoon’s work.
It admits what it is unsure about
Confidence is a band, not a decimal implying precision nobody has. Anything inferred is labelled as inferred. The gaps are part of the output, not missing from it.
No roadmap theatre
What works today
The chain from RFP to SOW is built end to end and running in production. Rather than let a feature list imply more, here is exactly where the line falls.
Built and workingv0.1
- The RFP taken apart — requirements, conditions, deadlines, service levels and evaluation criteria, each quoted from its source
- Missing information and internal contradictions, ranked, with the clarification questions to send
- Solution, scope, assumptions, risks, work breakdown and effort — proposed by AI, decided by you
- Cost, margin, discount and price calculated by the application, never by the model
- The proposal and the SOW as Word documents, in English or Turkish, versioned
- An automated review of requirement coverage and commercial consistency before you send
- The same documents as PDF, with the diagrams and the layout the Word file has
Not built yethonest about it
- A public API
- Semantic search across the knowledge base — today it is keyword search
- Change impact analysis — what a scope change does to effort and price
Nothing hides behind a “coming soon” button. Customer emailing, e-signature, CRM sync and single sign-on are absent because they are deliberately out of scope — not pending.
Pricing
Pay for the bid, not the seat
Your architect, your bid manager and whoever signs all work on the same proposal. Charging per head would tax the review that makes the output worth signing — so every plan has unlimited users, and what is metered is the proposal.
Trial
The whole chain, end to end, on an RFP of your own.
1 proposal
- No card required
- The full chain from RFP to SOW
- Word and PDF, in English and Turkish
Basic
For teams answering a tender or two a week.
5 proposals a month
- Unlimited users
- The full chain from RFP to SOW
- Word and PDF, in English and Turkish
Professional
For presales teams with a steady pipeline of bids.
20 proposals a month
- Unlimited users
- The full chain from RFP to SOW
- Word and PDF, in English and Turkish
- Priority when the queue is busy
Past the allowance, further proposals are $15 each — a bid does not stop halfway because a counter ran out.
For companies outside Turkey. Paid annually, 2 months are free and the price is fixed for the year.
Free during the pilot. These prices apply when it ends, and pilot teams hear from us first.
FAQ
Questions buyers ask
The things a bid manager, a finance lead and an IT security reviewer each want to know before a pilot.
Does the AI decide our prices?
No. It can recommend a margin or a contingency; the application does every calculation, and a price counts only once a person with the right role approves it. Change a term afterwards and the approval lapses.
Where is our data, and who can see it?
In Frankfurt (eu-central-1). Each company's data is separated by row-level security in the database itself, so one customer's documents are unreachable from another's account — not merely hidden by the interface.
Which documents can we upload?
PDF, Word (.docx), plain text, Markdown and CSV, up to 25 MB each. Scanned PDFs need OCR first — the text has to be selectable to be read.
Can we edit what it produces?
Everything. Every requirement, scope line, assumption, risk and document section can be accepted, edited, rejected or regenerated, and re-running a stage never overwrites what you have already reviewed.
Does it work in Turkish?
Yes. The interface is in English and Turkish, and proposals and SOWs can be generated in either — a Turkish integrator can answer an English tender, or the other way round.
How long does a proposal take?
About fourteen minutes of processing on a mid-sized tender, measured on the live service, plus your review. Larger tenders take longer.
What counts as a proposal on a plan?
A proposal counts once, when it is created — however many times you regenerate, edit or export it. Users are unlimited on every plan.
What does it deliberately not do?
It does not email customers, sign contracts or sync with a CRM. It prepares a bid you can defend; sending it stays with you.
Bring us a real RFP
The pilot is small on purpose: a handful of teams running live bids, close enough to talk to. What gets built next comes from what actually breaks, not from a roadmap.
- Free during the pilot
- Set up by a person, usually within a day
- Your documents stay inside your organization