Multika marketing squad graded the 15 main public pages on FEMS against two scorecards: content (clarity, buyer relevance, proof, trust, conversion) and visual (consistency, credibility, education fit, mobile risk, placeholder risk). Scored 1 (blocker) to 5 (launch ready).
Skip the scorecards if you want. Here’s the take.
No complaints. These don’t need work.
5 product pages (Student Journey, Teaching, Finance, HR, Campus Life), /product/app, /experience/try, /press/kit.
The homepage says “5,000+ daily users” and “99% uptime.” Product pages claim things like “process payments in seconds.” Multika is asking: are these numbers real and verified? Schools won’t trust round numbers without backing. Your call (or sales’) — not a code fix.
Very thin as a credibility page. No real coverage, no school logos, no proof anyone uses FEMS.
AI Center section still says “Coming Soon” / “architecturally ready”. Reads as future-state on a public marketing page. Blocked until the FEMS app rebuild lands.
Warm founder story, but the trust path is light: no real customer logos, no operating-history evidence, no governance signal.
Visual placeholders pull the page down. Video panel and role/problem cards still use ScreenshotPlaceholder blocks.
New V2 hero looks great. Two things to watch: it might be cramped on phones, and the stats (5,000+ users, 99% uptime) need to be real.
7-step flow on a narrow phone could feel tight. Final 375px check.
Long step labels could wrap badly on narrow phones. Final check.
Useful breadth, but proof and trust language is lighter than the finance / admin pages.
Strong for parents and students; weaker as a story for principals and IT admins.
CTA path is clear, but the form doesn’t tell people what happens after they submit.
Strong guided exploration. Confidence cues on demo guardrails need a final check.
Persona-appropriate quote path. People don’t know what to expect after submitting the form.
Works as a utility page for journalists. Not a buyer-proof page. Don’t lean on it for trust.
No issues. Launch ready.
Strong overall. Section detail is dense; do a final readability scan.
Grouped by who does the work.
Most of the website. 8 pages launch-ready as-is.
AI Center on /product/admin-control — waiting on FEMS app team to finish the underlying feature.
Three options. Pick one.
Fix the small stuff now. Homepage mobile hero test + form “what happens next” copy. About 1 hour. No outside help needed.
Send the bigger items back to Multika. I write the message asking the designer for /experience/watch assets and the writer for /about + /press copy.
Both A and B at the same time.