Enterprise DNA

Instead of AutoRFP.ai

Stop renting AutoRFP.ai. Own your tender response system.

We build your version around how your team responds, bring your AutoRFP.ai response records across and run it for you through Omni by Enterprise DNA. Start with the bids, reviews and evidence your business needs.

AutoRFP.ai Accelerate lists $1,299 a month paid yearly, or $15,588 a year. The vendor page does not identify the currency.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the subscription buys

AutoRFP.ai charges by project allowance, with unlimited users

Scale lists $899 a month paid yearly. Accelerate lists $1,299. Features and users are included across plans. Compare the annual commitment with the response work your team actually needs.

calendar_month

An annual commitment

The published monthly rates are paid yearly. Scale works out to $10,788 a year at the displayed rate.

folder

A project allowance

Scale includes 24 projects a year. Accelerate includes 50. A project covers a bid or questionnaire.

group

A shared response workspace

Unlimited users are included. Adding a reviewer is not a separate seat charge in the published plans.

library_books

Content and drafting features

The subscription includes unlimited content and all features. Your recurring bill keeps that workspace available.

link

Connected business systems

Single sign-on and integrations are included across plans. We scope the connections your own version needs.

support_agent

Implementation and support

The vendor includes implementation and support. Running your own version also needs a named operator and an agreed support plan.

Your own response records

Make the review process follow your business

Bid room

See the unfinished work before the deadline

Keep each bid, customer, owner and due date together. Review the work your team has committed to.

  • check List bids in deadline order
  • check Count questions that still hold a response
  • check Find overdue and unassigned questions
  • check Combine the bid decision, workload and retention review in your own weekly report

Answer library

Know where a reused answer came from

Store the answer with its source, owner, version and next review date. Keep its approval separate from the bid review.

  • check Search the wording already in your library
  • check Reuse a current approved answer
  • check Flag bids using a changed or expired library answer
  • check Keep the original bid wording while the new library version is reviewed

Response review

Put evidence behind each answer

The author records the source. A different reviewer checks the current response before it is ready.

  • check Hold blank answers and missing sources
  • check Clear approval when an answer changes
  • check Keep the recorded before-and-after history
  • check Record an external submission receipt only after the checks pass

Business paperwork

Prepare the review pack in your own format

Generate draft response packs, reviewer briefs and contact-data review sheets with your business name and colours.

  • check See the question, response and evidence together
  • check Draft a follow-up for a person to review and send
  • check Keep unfinished answers visibly marked
  • check Add your own fields, review rules and reports as the process changes

Make it yours

Design your own AutoRFP.ai replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from AutoRFP.ai. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your AutoRFP.ai replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your AutoRFP.ai data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real output from the fictional Harbour response team. The records and evidence references are demo examples.

forum

Tender Responses for Claude Code

Connected to your own database

Which tenders still need work before review?

Hill regional questionnaire

Customer
Fictional Hill Services
Owner
Ari
Due
2026-10-06
Questions
1
Blocked
1
Decision
hold: responses

Harbour support tender

Customer
Fictional Harbour Cooperative
Owner
Mere
Due
2026-10-15
Questions
3
Blocked
2
Decision
hold: responses

Ask it anything

Ten questions to ask your tender records

These questions work on the supplied demo. AutoRFP.ai also offers reports and content reviews. Owning the records lets you change the questions and rules around your own business.

chat_bubble Which bids depend on an answer whose library review expired?
chat_bubble Who owns the most unfinished responses?
chat_bubble Which tender has no questions and must stay held?
chat_bubble Which answers have no supporting source recorded?
chat_bubble Which questions are overdue and still unfinished?
chat_bubble Which requirements have no assigned owner?
chat_bubble Which library records have never received approval?
chat_bubble What did a response say before the last revision?
chat_bubble Which bids need a contact-data retention review?
chat_bubble Which tenders copied an older version of a changed library answer?

Switching

How to switch from AutoRFP.ai

A move usually involves exporting and mapping your questions and answers, checking the imported records, and handling any history or materials that need separate migration.

  1. 1

    Export your records

    Use AutoRFP.ai’s Excel Backup and save its question-and-answer sheet as a CSV export. If your account does not show that option, export what the account allows, usually CSV or Excel, and check with AutoRFP.ai. Include the questions and answers you want to carry over. Decide separately how much older bid history you need to bring.

  2. 2

    Test the mapping

    Before loading live records, run a trial import to check the spreadsheet’s column mapping. Map the export’s headers to the replacement’s question and answer fields, then correct any mismatches the trial identifies. The import validates the whole file before saving, so use that check to catch problems before records are added.

  3. 3

    Review the import

    Review the import’s validation results, then compare the imported questions and answers with your export and confirm they sit under the right bid. Check anything the import reports as invalid or unmapped before relying on it. Imported changes clear approval and evidence references, so plan to restore or recheck those records. Attachments, approval identities, library connections and customer document formatting need separate migration work.

  4. 4

    Run both systems

    Keep AutoRFP.ai and the replacement in use side by side for a short period on current work. Compare imported questions and answers with the active bids, and have your team check any differences before using a response. Treat each system as a separate record during this period. Approval identities need separate migration work, so do not rely on the import to carry them across.

  5. 5

    Switch off AutoRFP.ai

    Switch off AutoRFP.ai only after your team has checked the records it needs and agreed how to handle separate items such as attachments, library connections, approval identities and customer document layouts. Make sure the historical records you decided to keep remain available to your team in the replacement or another agreed location.

construction

Where the real effort goes

The main effort is usually not loading question-and-answer rows. It is mapping your own fields and review rules, deciding how much bid history to bring, and handling items the spreadsheet import does not cover, such as attachments, approval identities, library connections and customer document formatting. If you have Enterprise DNA install and run it, Enterprise DNA handles this migration work with you.

Not ready for a call?

Get your AutoRFP.ai switch plan by email

We will send you the step-by-step plan for moving your business off AutoRFP.ai, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Choose your level of help

Three ways to own your tender response system

Open source

Do it yourself

Free and open source

  1. 1 Clone the repo and run npm install and npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor
  3. 3 Save an AutoRFP.ai Excel Backup sheet as CSV and check its header mapping
  4. 4 Import into a fresh bid, add evidence sources and review the answers
Get it on GitHub

Built around your business

We customise it

A setup fee for your agreed scope

  • check Your response fields, review roles and bid rules
  • check Your AutoRFP.ai response records brought across with an agreed migration scope
  • check Your customer document formats and a web front end if the team needs one
  • check A different technology and connections to existing systems where needed
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Your response records connected to the rest of your business
  • check Access controls, backups and recovery checks configured for your team
  • check A team to maintain the process and build the next useful report
Talk to Sam

Questions

Instead of AutoRFP.ai, answered

Can we bring our AutoRFP.ai work across? expand_more

The free version imports questions and answers from a project backup saved as a spreadsheet export, after checking the column mapping. It validates the whole file before saving and recognises repeat imports. A real vendor backup was not available for this build, so we test your export before agreeing the switch. Attachments, library connections, approval identities and customer document formatting need separate migration work.

Does it write or submit the tender for us? expand_more

Your team prepares and verifies the answers. The free version stores them, reuses reviewed library answers and prepares draft packs. A person checks every claim and submits the customer’s required format. We can build the drafting assistance and connections your team needs into your version.

What happens when an answer changes? expand_more

Editing a response clears its approval. Changing a library answer keeps the earlier bid wording intact and flags affected responses for review. The author and reviewer must be different people. Their recorded names provide attribution, so shared use also needs authenticated access configured for your team.

Can we keep our document formats and security process? expand_more

We agree the required customer formats, identity controls and source connections before building your version. The free checks cover response evidence, review status and contact-data review dates. They do not certify security controls or confirm that a claim is true. Your reviewers remain responsible for the evidence.

What does Enterprise DNA charge, and who owns it? expand_more

The free version is open source. We agree a setup fee for installation, migration and custom work, followed by a retainer when we run it for you. You own your database and your version. Hosting and external services are scoped with you.

Bring one real tender to the conversation

Spend 30 minutes with Sam. Show us the response work you pay AutoRFP.ai for, the evidence your reviewers need and the documents you submit. We will map your version and the work involved in bringing it across.

Book 30 minutes with Sam Get the free version

Tender Responses for Claude Code is free and open source, published by Enterprise DNA.

Done paying for AutoRFP.ai?

Get your version built