Arion Educational Hub — project overview
One page for the client team: what the site contains, what the build costs, and what is needed to start. Please give feedback per section number or table row.
| Page | Sections (in order) | Conversion goal |
|---|---|---|
| Home | Hero with product explanation · USP bar · Audience cards · Popular topics · How it works + figures · FAQ | Route visitors to the right path |
| Patients | Hero · Product selector · Videos · Challenges + steps · Product overview (13) · Where to buy · FAQ · Support band | Find a retailer / call |
| Professionals | Hero with evidence · Profile tabs · Guidelines · Steps + videos · Quotes · Product selector · Demo/sample form | Demo or sample request |
| Distributors | Hero with onboarding promise · Business case · Range · Selector · Staff training · Toolkit · Reviews · FAQ · Form | Reseller enquiry |
| Contact | Three routes (patient / clinical / sales) · Address block | Right channel per audience |
Added in production: FAQ and VideoObject schema, sitemap, separate URLs per article/video/product, audience memory, and analytics on quiz steps and forms.
Basis of this estimate: build in Bricks Builder with reusable components; the approved blueprint (design system, 16 sections, quiz logic) is reused; design and advisory phase are billed separately; the client supplies content complete and on time. Conditions: fixed scope after sign-off and a maximum of two feedback rounds per phase. Interim change requests outside the scope are welcome; they are billed per hour and always itemised, so you can see exactly what every hour was spent on. You only pay for hours actually worked — so you never pay too much.
Honest about the bandwidth: these hours are calculated per phase on the basis of the approved blueprint — no guesswork, no hidden margin. In practice the total may come out around 10 hours lower or higher. What decides that lies largely with all of us together: how complete and timely content and materials are delivered, how often things change along the way, what gets added, and how complex any extra design wishes are. If the project runs smoothly, you see it back in the hours. If it threatens to grow, we flag it up front — never afterwards on the invoice.
| Phase | Description | Hours |
|---|---|---|
| 1. WordPress + Bricks setup | Installation, child theme, staging environment | 4 |
| 2. Design system in Bricks | Global classes & variables (colours, typography), reusable components | 7–8 |
| 3. Hub page | Hero, USP bar, audience cards, popular topics, FAQ — built from components | 4–5 |
| 4. Patient page | Accessible build (65+), video sections, product overview, where-to-buy | 6–7 |
| 5. Professionals page | Patient-profile tabs, clinical guidelines, step-by-step, demo/sample form | 7–8 |
| 6. Distributor page | Business case, product range, toolkit, FAQ, enquiry form | 7–8 |
| 7. Product selector (quiz) | Code element in Bricks: branching logic, three audiences, safety check | 8–9 |
| 8. Forms & mail integration | Bricks Forms, validation, notifications, GDPR-compliant consent | 5–6 |
| 9. Technical SEO | Schema markup (FAQ, VideoObject), metas, sitemap, performance | 5–6 |
| 10. Content structure | Custom post types + loop templates (products, videos, FAQ) | 6–7 |
| 11. QA & accessibility | WCAG check, cross-browser and mobile testing, correction round | 5–6 |
| 12. Go-live | DNS, analytics, cookie consent, handover | 2 |
| Subtotal build | 66–76 | |
| Project management (approx. 12%) | Planning, client communication, coordinating feedback rounds | 8–10 |
| Indicative total | 74–86 hours |
| Optional extension | Description | Hours |
|---|---|---|
| Multilingual — first additional language | Translation-plugin setup, Bricks templates, ACF/quiz config per language, hreflang and QA (translations supplied) | 14–18 |
| Multilingual — each subsequent language | Content entry into the working language structure (translations supplied). Indication applies to the current scope; on commissioning we re-estimate based on the pages, articles, forms and features present at that time — and on the text length of the language (German requires extra layout checks) | 8–12* |
| Retailer locator with map | Postcode search, map integration, manageable retailer list | 7–10 |
| Blog / knowledge-base module | Custom post type with archive and detail templates from the design system, categories, simple search | 8–12 |
* Snapshot: the site grows and translation hours grow with it. The final per-language estimate follows at the moment of commissioning, based on the content and features present at that time.
Indicative lead time: 6–9 weeks after sign-off, depending on content delivery. No rights can be derived from this estimate; it serves as the basis for the final quotation.
Label "Client" = supplied by the client · "Us" = handled or advised by us. Missing deliveries shift the planning, not the quality.