Flowgear wwwnext: five-page conversion review

Intended funnel

1. Land with clear Integration IDE + governed AI positioning.
2. Build trust (Gartner, logos, customer stories).
3. Self-segment (build, Builder MCP, engineering, assessment).
4. Convert on Start Building or secondary See Pricing.

Element task list

Element	Issue	Recommendation	Priority
Hero H1	Speed/AI angle is strong; IDE label may lag for ops and finance buyers	Lead subhead with business outcome (governed integrations, quote-to-cash), then IDE	High
Hero subhead	Live copy uses em dashes (CI violation)	Rewrite with commas or colons; see CI flags	High
Primary CTAs	"Start Building" and "See Pricing" are clear; buttons do not state the offer	Test "Start free for 90 days" and "Compare plans"	Quick
Nav	"Book a meeting" competes with self-serve trial	Split intent: "Start free" vs "Talk to sales" in nav	High
Gartner strip	Proof is strong; link affordance is weak	Clickable block + "Verified on Gartner Peer Insights"	Quick
Logo marquee	Credibility without industry context	One line: teams in manufacturing, finance, retail	Quick
Where the value moved	Strong thin vs durable framing	Mini-CTA on durable column: "See the governed runtime"	Medium
Build with AI	Approval message is buried in bullets	Callout: "Every change is yours to approve before it ships"	High
IDE and MCP sections	Long scroll before repeat CTA	Mid-page primary CTA after MCP section	High
Find your path	Three paths have equal weight	Badge "Most teams start here" on build card	Medium
Case study carousel	Quotes are strong; industry is secondary	Title format: Industry + outcome; mobile "Read story" higher	Medium
Brands grid	Long list, low scan value	Curate 8-12 logos + "and enterprise customers worldwide"	Low
Final CTA	Message repeats well	Microcopy: credit card signup, no sales call, cancel anytime	Quick
Footer	Many paths compete with trial	Lighter footer on homepage vs product pages	Low

Quick wins

• Fix hero and body em/en dashes for CI compliance.
• Add trial microcopy on primary CTA and final band.
• Make Gartner strip fully clickable with verification label.
• Pull human-in-the-loop approval into Build with AI subhead.

High-impact changes

• Clarify nav hierarchy: self-serve trial vs sales meeting.
• Add mid-page CTA after MCP section.
• Hero subhead A/B: outcome-first vs speed-first.
• Emphasize default path in "Find your path" with visual hierarchy.

PIE research backlog

Rank	Hypothesis	P	I	E	Total
1	Outcome-first hero subhead raises trial starts for cold traffic	8	9	6	23
2	Nav label split reduces meeting clicks that should be trial	7	8	7	22
3	Mid-page CTA recovers scrollers who never reach footer	8	7	8	23
4	Approval callout increases trust for AI-skeptical buyers	7	7	9	23
5	Moderated usability (5-8 sessions) on staging validates confusion on IDE vs MCP	6	8	5	19

Copy alternatives (Flowgear CI, US English)

Hero subhead

Primary CTA

CI flags on live copy

Location	Violation	Suggested fix
Hero subhead	Em dash between clauses	Use comma: "...depends on. AI does the heavy lifting..."
Build with AI bullets	Possible em dash in "build, test and repair" line	Use colon or period between ideas
Customer quote attribution	Middle dot in "Operations Director · Safe Life Defense"	Acceptable punctuation; not an em dash
Throughout site	En dash in numeric ranges in other pages	Use hyphen: "12-18 month" on assessment cross-links from homepage

Post-launch experiments

• Hero: outcome-first vs speed-first (needs traffic for significance).
• Nav: single dominant trial CTA for paid campaigns.
• Mid-page CTA: on vs off (scroll depth + trial start rate).

GE note: pair with analytics-tracking for start_building_click and trial completion events before testing.

Intended funnel

1. Confirm predictable pricing (no metered surprises).
2. Understand enabled workflows, concurrent workflows, and Sustained CPU.
3. Select plan band.
4. Convert on Start Building or Talk to Sales.

Element task list

Element	Issue	Recommendation	Priority
Draft banner	"Pricing under review" erodes trust on a conversion page	Remove on production; use dated "New pricing" if needed	Critical
Hero	Promise is clear; cognitive load hits immediately	One line under H1: solo builders through enterprise programs	Quick
Plan cards	Five tiers plus Sustained CPU bands on each card	Single explainer above grid; collapsed band on cards	High
Sustained CPU	Novel metric repeated on every card; three-dial model is dense	One interactive explainer above grid; cards show selected band only	High
Dedicated CPU callout	Strong differentiator vs millicore competitors	Pull "Dedicated CPU, spikes are free" proof line closer to plan grid	Medium
Build plan	"First 90 days free" is strong; $200/mo after is easy to miss	"Then $200/mo" plus trial vs paid feature list	High
Concurrent vs enabled	Industry-specific language; third dial adds complexity	Reuse "How the two dials work" diagram directly under comparison table; clarify third dial in FAQ	High
Most popular	On Growth tier	One-line why: SSO, 20 concurrent workflows, priority support	Quick
Scale vs Enterprise	Sales-led is clear	"Typical buyer" line on each card	Medium
Compare table	38 features, horizontal scroll on mobile	Sticky first column; top-row "key differences" summary	Medium
V1/V2 FAQ	Critical for existing customers; buried in accordion	"Migrating from V1?" link beside plan selector	High
FAQ accordion	Strong answers on overages, dedicated machines, monthly average	Surface 3 FAQs under cards: no overages, free start, what happens if you cross your band	Medium
CTAs	Good split between build and sales	Enterprise secondary: "Book a pricing review"	Quick
Bottom CTA	Trial and assessment compete	Split bands: "Ready to build?" vs "Need a roadmap first?"	Medium

Quick wins

• Remove or replace draft banner before any external traffic.
• Add "Then $200/mo" on Build after trial callout.
• Inline three FAQ answers under plan grid.
• Add "why most popular" line on Growth.
• Move dedicated CPU proof line adjacent to plan selector.

High-impact changes

• Unify Sustained CPU education into one module above plans.
• V1 migration link at top of page for existing customers.
• Simplify plan card UI (less repeated copy per tier).
• Split bottom CTA by intent (build vs assessment).
• Clarify three-dial model (enabled workflows, concurrent workflows, Sustained CPU) in one visual.

PIE research backlog

Rank	Hypothesis	P	I	E	Total
1	Removing draft banner improves trust and click-through to Start Building	9	9	9	27
2	Single Sustained CPU explainer reduces plan-selection abandonment	8	9	6	23
3	V1 migration link at top cuts support tickets and wrong-plan signups	7	8	8	23
4	FAQ diagram above fold clarifies concurrent workflows vs Sustained CPU	7	7	7	21
5	Card sorting test with 6 finance/IT buyers on capacity language	6	8	5	19

Copy alternatives (Flowgear CI, US English)

Hero subhead

Build plan microcopy

Sustained CPU tooltip (inline)

Bottom CTA bands

• Build band headline: "Ready to build at the speed of AI?"
• Assessment band headline: "Need a map before you scale workflows?"

CTA: "Book an Integration Assessment"

CI flags on live copy

Location	Violation	Suggested fix
Draft banner	"feedback and may still change" undermines Zero Risk sweep	Remove on production
Plan capacity tooltips	Long sentences with em dashes in live pricing FAQ cross-links	Audit FAQ answers; use periods between clauses
Effective monthly price line	En dash possible in numeric ranges elsewhere	Use hyphen for numeric ranges
"Dedicated CPU · this month"	Middle dot separator	Acceptable punctuation; not an em dash

Post-launch experiments

• Sustained CPU explainer: interactive vs static diagram.
• Build card: explicit post-trial price vs control.
• Growth "most popular" with reason line vs badge only.
• Three-dial education: above grid vs FAQ-only.

Defer price point tests until capacity UX is understood qualitatively.

Intended funnel

1. Confirm SAP Business One fit (on-prem, HANA, SQL, hybrid).
2. Scan use cases by department (sales, CRM, logistics, finance, data capture).
3. Trust via customer stories (FIGJAM Mobile, Leatt Corp, ECN).
4. Resolve objections in FAQ (Service Layer vs DI API, assessment vs trial).
5. Convert on Start Building.

Element task list

Element	Issue	Recommendation	Priority
Hero H1	Clear ERP positioning; strong for organic "SAP Business One integration"	Keep; ensure paid keyword message match on connector LPs	Medium
Hero subhead	Outcome-led; three bullets cover deployment patterns well	Add one hybrid/on-prem reassurance line above fold for IT buyers	Medium
Hero CTAs	Generic site-wide "Start Building"	Primary: "Build SAP Business One integration"; secondary: "All connectors"	High
Eyebrow	"Deep dive · ERP Connector" works	Add deployment hint if accurate: "HANA, SQL, on-prem, and cloud"	Low
In-page nav	Use cases, Why, Customers, FAQ structure is good	Active section highlight on scroll; sticky nav on desktop	Quick
Use case grid	Five categories, 15 patterns, strong depth	"Start here" tags on order-to-cash (quote-to-order) and web/marketplace orders	Medium
Why integrate	Three outcome columns; no quantified proof	Pull one approved metric or quote from Leatt or FIGJAM above fold	High
Node documentation	Good for technical evaluators	Move "Read the node documentation" link into hero zone for developer persona	Medium
Customer stories	FIGJAM, Leatt, ECN are relevant and SAP-specific	One quote in hero or immediately below: Leatt four-week delivery angle	High
FAQ	Strong coverage of Service Layer, HANA/SQL, on-prem hybrid	Expand sandbox, bulk limits, and object coverage as separate FAQs if docs support	Medium
Assessment cross-sell	FAQ mentions assessment vs trial	Inline comparison chip: "Need a full-estate map? Book an Integration Assessment"	Medium
Social proof	No Gartner or Peer Insights strip on connector page	Reuse homepage Gartner band below hero	Quick
Final CTA	Site-wide closer	"Prove one SAP Business One workflow in 90 days" with trial microcopy	Quick

Quick wins

• Connector-specific primary CTA label.
• Gartner or Peer Insights strip below hero.
• "Start here" tags on quote-to-order and web/marketplace order use cases.
• Final CTA tied to 90-day trial and no sales call.
• Assessment vs trial chip in FAQ zone.

High-impact changes

• Hero or sub-hero quote from Leatt or FIGJAM customer story.
• Approved proof line in "Why integrate" section.
• FAQ expansion for technical evaluators (sandbox, bulk, API limits).
• Paid landing variant without full mega nav for ERP keyword campaigns.

PIE research backlog

Rank	Hypothesis	P	I	E	Total
1	SAP-specific CTA raises trial starts from connector organic traffic	8	8	9	25
2	Hero customer quote increases scroll to use cases and FAQ	7	8	8	23
3	On-prem/hybrid reassurance in hero reduces bounce from IT evaluators	7	7	8	22
4	Doc link above fold helps developer-led evaluations complete trial signup	6	7	8	21
5	Competitive benchmark vs native SAP and iPaaS connector pages (5 pages)	5	7	6	18

Copy alternatives (Flowgear CI, US English)

Hero subhead

Primary CTA

Final band

• Headline: "Ready to connect SAP Business One to the rest of your stack?"
• Subhead: "Start free for 90 days. No sales call. Build and approve in the Integration IDE."

CI flags on live copy

Location	Violation	Suggested fix
Eyebrow	Middle dot in "Deep dive · ERP Connector"	Acceptable punctuation; not an em dash
Use case headings	"Sales & E-commerce" uses ampersand	CI allows ampersand only in official names; consider "Sales and E-commerce"
FAQ answers	Check long answers for em dashes	Split into two sentences with periods
Customer story cards	"Read the story →" arrow is fine	No dash violation
Cross-links	"12-18 month" roadmap mentions on assessment links	Hyphen only for numeric ranges

Post-launch experiments

• Hero CTA: generic "Start Building" vs SAP-specific label.
• Use case order: sales-first vs finance-first for paid ERP audiences.
• Full nav vs lite nav on connector paid landing pages.
• Hero quote: Leatt manufacturing vs FIGJAM distribution angle.

Organic traffic: H1 already matches intent; focus on CTA specificity, proof placement, and on-prem reassurance.

Intended funnel

1. Confirm quote-to-cash and CRM-ERP friction as the problem.
2. See connected systems (CRM, ERP, finance, billing, marketing, support, BI, eSignature).
3. Scan workflow patterns by category (CRM sync, quote-to-cash, pipeline, lead nurture).
4. Resolve objections in FAQ.
5. Convert on Book Integration Assessment or Start Building.

Element task list

Element	Issue	Recommendation	Priority
Hero H1	Strong quote-to-cash angle with AI governance	Keep; fix grammar in supporting line (see CI flags)	High
Hero body	Long paragraph; two intents (build vs assess) blended	Split: outcome paragraph, then one line on who this page serves	Medium
Audience line	Good friction framing; "here's" is lowercase mid-sentence	Fix capitalization and punctuation; style as callout	High
Hero CTAs	"Book Integration Assessment" and "Start Building" have equal weight	Primary/secondary hierarchy: Assessment for leadership traffic, Start Building for builders; add micro-labels	High
Proof near CTAs	No Gartner, case study metric, or customer quote above fold	Compact trust strip: Gartner rating, one quote-to-cash outcome, Microsoft partner badge	High
Systems strip	CRM, ERP, Finance, etc. listed well	Add one-line "typical stack" example: Salesforce + SAP + Xero style pattern	Quick
Workflow sections	Four strong groupings with 2-3 patterns each	"Start with this" on CRM-to-ERP handoff and live pricing during quoting	Medium
Mid-page outcome block	Reinforces customer-fact alignment	Add CTA repeat: "Book Integration Assessment" for roadmap buyers	Medium
FAQ	Four solid answers; assessment path underplayed	Add FAQ: "When should sales teams book an assessment vs start building?"	Medium
Explore more	Good internal links	Prioritize Integration Assessment and CRM integration cards visually	Quick
Bottom band	Assessment pitch is strong but competes with Start Building	Split bands: "Need a roadmap?" vs "Ready to build one workflow?"	High
Final CTAs	Start Building and See Pricing	See Pricing is weak for department page; use Assessment + Start Building	Medium

Quick wins

• Fix hero grammar: capitalize "Here's" and tighten audience line.
• Add compact trust strip below hero (Gartner, one case metric, partner badge).
• CTA micro-labels: "For leadership" on Assessment, "For practitioners" on Start Building.
• "Start with this" tags on quote-to-cash and CRM-to-ERP patterns.
• Split bottom CTA bands by intent.

High-impact changes

• Hero CTA hierarchy by visitor type (assessment primary for leadership campaigns).
• Dedicated Assessment vs Start Building decision module above fold.
• Approved customer quote with quote-to-cash outcome near hero.
• FAQ expansion linking assessment to multi-department quote-to-cash programs.

PIE research backlog

Rank	Hypothesis	P	I	E	Total
1	Assessment-primary CTA hierarchy improves qualified bookings from leadership traffic	8	9	7	24
2	Trust strip below hero increases scroll to workflow sections	7	7	9	23
3	Assessment vs Build decision module reduces wrong-fit trial signups	7	8	6	21
4	"Start with this" tags on quote-to-cash patterns raise assessment inquiries	6	7	8	21
5	Moderated usability (5-8 sessions) with sales ops buyers on CTA confusion	6	8	4	18

Copy alternatives (Flowgear CI, US English)

Hero H1

Audience callout (replaces live lowercase line)

Primary CTA pair

• Assessment (primary): "Book Integration Assessment" with microcopy "Get a prioritized roadmap in two weeks"
• Build (secondary): "Start Building" with microcopy "Prove one workflow free for 90 days"

Bottom band split

• Assessment band headline: "Not sure which integrations to prioritize?"
• Assessment band CTA: "Book Integration Assessment"
• Build band headline: "Know your first workflow? Start in the IDE."
• Build band CTA: "Start Building"

CI flags on live copy

Location	Violation	Suggested fix
Audience line	"here's" lowercase after period	"Here's" or rewrite: "Here is how you connect CRM..."
Hero H1	Comma splice in long headline	Acceptable; optional split into H1 + subhead
Systems list	"Marketing Automation" and "Support Desk" are fine	No dash violations
FAQ answers	Check for em dashes in long clauses	Use periods between ideas
UK spelling	"fulfilment" in body copy	US English: "fulfillment" per Flowgear CI

Post-launch experiments

• Hero CTA: equal weight vs Assessment-primary hierarchy.
• Trust strip: on vs off (scroll depth and assessment bookings).
• Bottom bands: split vs single combined CTA block.
• Paid traffic: department page with lite nav vs full site nav.

Primary KPI for leadership campaigns: qualified assessment bookings. For practitioner campaigns: trial starts with quote-to-cash use case selected.

Intended funnel

1. Qualify as roadmap buyer (not trial-first).
2. Understand five-step engagement and deliverables.
3. Review sample assessment.
4. Convert on Book an Assessment (secondary: View Sample Assessment).

Element task list

Element	Issue	Recommendation	Priority
Hero	Strong AI + roadmap angle; price is below fold	Add "Typically $3,000-$4,000" in hero for qualification	High
Audience line	"For the buyer who wants a business outcome and a roadmap, not to build it themselves" is excellent	Visual callout so trial seekers self-select out	High
Primary CTAs	Book + View sample work well	Tertiary: "Start 90-day build trial" for wrong-fit traffic	Medium
Five-step process	Clear numbered flow (Discover through Present)	Week 1 / Week 2 timeline labels on steps	Medium
Deliverables	Screenshots of scorecard, backlog, and roadmap build trust	Tag each with role: CTO, ops, finance	Medium
Sample assessment	"View a Sample Assessment" and "Explore the full sample" links present	PDF or page thumbnail preview above fold	High
When to use cards	Good scenarios (many departments, manual reporting, pre-scale)	Anchor links to matching FAQ entries	Quick
Post-roadmap paths	Self-deliver, Flowgear deliver, partner deliver reduces risk	Add "No obligation to buy Flowgear" near paths	Quick
vs free trial	Mentioned in FAQ on other pages; thin on this page	Comparison block: Assessment vs 90-day Build	High
Pro services	Cross-link at bottom	Move "Have Flowgear deliver it" higher for enterprise visitors	Low
Trust	"Delivered by Flowgear or authorized partner" in body	Add one approved assessment buyer quote if available	High
Bottom CTA	Repeats hero CTAs well	Add price range reminder in final band	Quick

Quick wins

• Price range in hero.
• Sample assessment thumbnail above fold.
• Comparison block vs free trial.
• Callout for non-builder audience.
• "No obligation" near post-roadmap paths.

High-impact changes

• Assessment vs Build decision module above fold.
• Role labels on deliverable screenshots.
• Testimonial from assessment buyer (if approved).
• Week 1 / Week 2 timeline on five-step process.

PIE research backlog

Rank	Hypothesis	P	I	E	Total
1	Hero price range improves qualified bookings and reduces unqualified calls	8	9	9	26
2	Assessment vs Build table reduces trial signups from roadmap buyers	7	8	7	22
3	Sample thumbnail increases View Sample then Book conversion	8	7	7	22
4	Sales interview: 5 buyers on "what almost stopped you booking"	6	9	4	19

Copy alternatives (Flowgear CI, US English)

Hero subhead

Primary CTA

Assessment vs Build (comparison headline)

• Headline: "Not sure whether to assess or build?"
• Build column: "You know what to automate. Start free for 90 days."
• Assessment column: "Many departments, no clear order. Start with the roadmap."

CI flags on live copy

Location	Violation	Suggested fix
Hero body	Possible em dash in "roadmap, not to build" style clauses	Use comma: "outcome and a roadmap, not to build it yourself"
Deliverable captions	"12-18 month" in sample copy	Use hyphen: "12-18 month" (hyphen, not en dash)
Five-step section	Check step descriptions for dashes	Full stops between ideas
"Present Findings & Roadmap"	Ampersand in step title	Consider "Present Findings and Roadmap" per CI

Post-launch experiments

• Hero with vs without price range (booking quality metric).
• Sample thumbnail vs text link only.
• Tertiary trial link: on vs off (trial contamination rate).

Primary KPI: qualified assessment bookings, not volume alone.