Skip to content
SiteList

ProposAI Review: strong product, slow mobile performance (79/100)

ProposAI scores 79/100, with clear tender-response positioning, strong decision support and evidence-oriented review content. Its most material weakness is mobile performance: the homepage reaches LCP at 4.17s and takes 11.1s to become interactive.

Reviewed by SiteList Engine · 11 of 13 dimensions · published Reviewed on October 14, 2026

Is this your site?

Claim it

Quick facts

ProposAI is an AI tender and RFP response software site for bid teams.

Fact Value
Domain proposai.io
Category AI tender and RFP response software for bid teams
Pricing Paid; free entry plan and paid monthly plans
Pages crawled 22
Crawl date 2026-10-12
Evidence
Pages crawled
22
Crawl date
2026-10-12

Executive summary

ProposAI is a strong, clearly positioned product for structured tender and RFP work, scoring 79/100 overall. Its strongest public dimensions are technical SEO at 91/100, review-content integrity at 86/100, audience and messaging at 86/100, and first impressions and positioning, usability, accessibility and decision-support surfaces at 84/100.

The site gives bid teams a coherent path through category, workflow, pricing, file types, collaboration, review, security and signup. Its language is specific about tender packs, DOCX/PDF/XLSX, buyer order, evidence and review risks. The main trade-off is performance: mobile LCP is 4.17s and interactivity takes 11.1s, while desktop is much stronger. Design execution, writing quality and editorial QA are also fair-to-strong rather than standout, at 74/100, 70/100 and 78/100 respectively.

Evidence
Overall score
79/100
Technical SEO
91/100
Mobile LCP
4.17s
Time to interactive
11.1s

01 · First impressions & positioning — evidence-led findings

ProposAI makes its category clear within seconds: it calls itself “AI tender & RFP response software” and pairs that with drafting from the visitor’s own evidence and a buyer-style review. The homepage adds named customers and the concrete example of 46 questions ready, 38 sourced answers and 4 open risks. Keep this specific tender-response language on low-context surfaces and extend the existing ChatGPT and Claude comparison toward specialist bid tools.

Evidence
score
84/100
workflow
46 questions ready; 38 sourced answers; 4 open risks

02 · Audience & messaging — evidence-led findings

A bid-team lead can identify the product, understand its workflow, see a price entry point and check core trust questions from the main navigation. The homepage covers reading packs, mapping requirements, evidence-led drafting and buyer-style review. Pricing shows £0, £49.95 and £99.95 monthly plans, while the FAQ addresses file support, collaboration, security, hosting and model training. Add a wider specialist comparison using workflow, evidence control and review depth.

Evidence
score
86/100
plans
£0, £49.95, £99.95 monthly

03 · Usability — evidence-led findings

ProposAI’s core routes are easy to follow: the homepage exposes Start free and View pricing, Pricing is one click away, and the primary navigation keeps Product, Pricing, Blog, FAQs and About visible. Pricing presents three clear plans. The main cost is mobile readiness: PSI records 4.17 s LCP, 11.1 s Time to Interactive and 520 ms TBT. Add a team-size or proposal-volume cue beside each plan and improve the critical path.

Evidence
LCP
4.17 s
TTI
11.1 s

04 · Accessibility — evidence-led findings

The sampled pages expose header, navigation, main and footer landmarks, and image facts report zero missing alt attributes. The verified weakness is colour contrast: PSI gives the color-contrast audit a score of 0 on the homepage and sampled blog article. The same pages report no skip link, and About jumps from h1 to h3. Add a first-focusable skip link, correct the heading sequence and repair each failing contrast pair. Manual keyboard and screen-reader checks were not verified.

Evidence
missing alt attributes
0
About headings
h1 → h3 → h3 → h3 → h2

05 · Design execution — evidence-led findings

ProposAI has a recognisable green-and-cream system, strong desktop hierarchy and repeated Geist, Newsreader and Geist Mono roles. At 390px there is no horizontal overflow. Execution loses ground on details: the homepage has 22 small tap targets and Pricing has 43, including 18×18px tooltip buttons. The inventory contains 81 colours, 38 font sizes, 19 radii and 48 spacing values. Raise hit areas to 44px, consolidate tokens and add image dimensions.

Evidence
homepage small targets
22
pricing small targets
43

06 · Performance — evidence-led findings

Mobile delivery is ProposAI’s clearest weakness: the homepage reaches LCP at 4.17 s and becomes interactive at 11.1 s, while desktop homepage LCP is 0.68 s. PSI records 515 ms homepage TBT and 407–425KiB of estimated unused JavaScript. The homepage network log totals 11,358KiB across 94 requests and 20 blocking requests. Make the LCP request discoverable early, defer non-critical work, split route code and add image dimensions. Field CrUX was unavailable.

Evidence
homepage mobile LCP
4.17 s
network summary
11,358KiB across 94 requests; 20 blocking requests

07 · Writing quality — evidence-led findings

ProposAI’s strongest copy uses concrete nouns: tender packs, DOCX/PDF/XLSX, buyer order, evidence and review risks. The sequence Read the pack, Map every requirement, Draft with evidence, then Review like a buyer gives the workflow shape. The main weakness is density: N1 reports 621 words in one extracted homepage paragraph, 694 on the FAQ and 815 on the ITT article. Restore visible paragraph and list boundaries, link security claims to evidence and reduce sign-up to one H1.

Evidence
homepage paragraph
621 words
FAQ paragraph
694 words
sign-up H1 count
2

08 · Decision-support surfaces — evidence-led findings

Pricing gives buyers real decision variables: active projects, uploads, members, AI drafts, Buyer Reviews and processing runs. The ChatGPT/Claude article fairly acknowledges that a general assistant can suit occasional, low-risk drafting. The missing layer is defended guidance: Bid-Manager is marked Most Popular without a supplied reason, and the comparison lacks a compact scenario verdict. Add choose-this-when guidance, name upgrade trade-offs and document the annual state; only the monthly view is evidenced despite a save 10% toggle.

Evidence
comparison scope
Eight workflow areas
annual pricing
save 10% toggle; monthly state evidenced

09 · Review-content integrity — evidence-led findings

Buyer Review is presented as an evidence chain connecting buyer-order questions, approved collateral, source-linked drafts and buyer-readiness findings. The illustrative panel shows 46/46 ready, 38 answers sourced and 4 open risks. The integrity gap is calibration: green, amber and red signals are decision support, not a buyer’s actual score or a substitute for human review, yet no calibration data or false-positive rates are supplied. Add a limitations note and separate observed facts from illustrative claims.

Evidence
readiness panel
46/46 ready; 38 answers sourced; 4 open risks
calibration evidence
No calibration data or false-positive rates supplied

10 · Editorial QA of content — evidence-led findings

The corpus has a consistent operational voice and earns trust through concrete contrasts, such as the Word questionnaire, PDF specification and spreadsheet pricing. The largest blocks need a clearer reading rhythm. N1 reports 621 words in one homepage paragraph and 815 in one ITT-article paragraph; split them into shorter paragraphs, lists, or answer blocks where appropriate.

Sign-up has two H1 elements; reduce the route to one H1 and demote the additional heading. Reported titles reach 77 and 73 characters. About’s security statements should be presented as stated product claims unless each is linked to direct supporting evidence. No supplied evidence establishes a schema-content mismatch or fabricated citation.

Evidence
homepage paragraph
621 words
longest titles
77 and 73 characters

11 · Technical SEO — evidence-led findings

The sampled technical foundation is strong. Public pages returned HTTPS 200 responses, and raw-versus-rendered word counts matched across key templates, showing no rendering gap. Samples also show prerendering, nosniff, HSTS-equivalent TLS delivery and cacheable responses. The opportunities are normalization and metadata polish: /how-it-works/ returns 200 without redirect, blog titles run 68–77 characters, and transactional variants reuse metadata while remaining noindexed. Choose one slash policy, redirect the alternate URL and tighten affected titles.

Evidence
public responses
HTTPS 200
slash variant
/how-it-works/ returns 200 without redirect
blog title range
68–77 characters

Verdict — 79/100: strong product, slow mobile performance

ProposAI is positioned for bid teams and organisations that answer structured tenders, RFPs and questionnaires, with a clear workflow and evidence-oriented review framing. The site earns its position through specific audience and product messaging, guided decision support, strong technical SEO, and a review narrative built around requirements, approved collateral, source-linked claims, coverage and buyer-readiness findings.

The fixable weaknesses are concentrated in mobile performance, where the homepage reaches LCP at 4.17s and takes 11.1s to become interactive; design execution, writing quality and editorial QA are also less consistent than the site's positioning and technical foundation. ProposAI is best suited to bid teams that value a focused tender-response workflow.

Evidence
Overall score
79/100
Performance score
61/100
Design execution score
74/100

Methodology & data notes

This 11-dimension review synthesizes supplied crawl evidence from 22 pages completed on 2026-10-12, together with the public dimension score table and its one-line summaries; it does not represent a fresh independent re-audit of every underlying check. The review covers positioning, messaging, usability, accessibility, design execution, performance, writing quality, decision-support surfaces, review-content integrity, editorial QA and technical SEO among the published dimensions.

Google Search Console was not connected, so no GSC enrichment was available. Read How SiteList scores for the review method and data notes.

Evidence
Review dimensions
13
GSC connected
false

Questions buyers actually ask

Who is ProposAI for?

ProposAI is aimed at bid teams and organisations that answer structured tenders, RFPs and questionnaires.

What does ProposAI help with?

The site presents ProposAI as AI tender and RFP response software, covering workflow, file types, collaboration, review, security and signup.

How strong is ProposAI's mobile performance?

Mobile performance is the clearest weakness in the review. The homepage reaches LCP at 4.17 seconds and takes 11.1 seconds to become interactive in the mobile lab runs.

Is ProposAI paid?

ProposAI uses a SaaS subscription model with a free entry plan and paid monthly plans. The supplied site facts classify its pricing model as paid.

How was ProposAI reviewed?

This is an 11-dimension review based on a crawl of 22 pages on 2026-10-12, using the public dimension score table and its one-line findings.

How this review was made

SiteList reviewed proposai.io on October 14, 2026 — pages, screenshots, performance runs, structured data and public records — then scored it across 11 of the 13 public dimensions. Every claim above is sourced from what we collected; nothing is hand-tuned and the score is never for sale.

Not covered in this write-up: Risk & stability (could not be assessed), Docs & self-serve help (not assessed). Dimensions without a score are excluded and their weight is redistributed across the scored ones.

Pending enrichment (data we could not fetch this run): SERP competitor lookups were unavailable., Paid audience and traffic enrichments were not provided., SERP and audience-language enrichment was unavailable or returned no useful brand results., Live Playwright execution of signup and FAQ accordion interactions, Mobile navigation DOM and tap-target verification, Run axe-core against representative desktop and mobile pages to identify the exact contrast pairs and any ARIA reference errors., Run a scripted keyboard tab-order probe, including focus visibility, skip-link behavior, menus, and dialogs., Test with a screen reader to verify announcements and interactive state changes.…

Read the full methodology

79/100ProposaiJump to review