Ficus Health
I built Ficus Health’s multilingual marketing website and content system for an AI documentation product used by clinical teams.
Make a specialist product easier to understand, evaluate and enquire about. I help Leeds teams turn technical material into useful website pages, connected demos and content they can maintain.
Trusted by teams doing serious work









I built Ficus Health’s multilingual marketing website and content system for an AI documentation product used by clinical teams.
I designed and built WithPower’s Webflow content hub, structuring guides, publications and podcasts into editable collections with category and subscription routes.
For Leeds health, digital and specialist-service teams, a website often needs to speak to both technical reviewers and the people using the product. Give each audience a clear route through use cases, evidence and practical questions. I work remotely from London.
Give technical reviewers, end users and buyers the information they each need.
Connect product explanations with research, guides and relevant use cases.
Collect useful context and send it to the team that can act on it.
Swipe to read more
Read all 14 reviewsMake the website useful both before and after someone sends an enquiry.
Separate product, use-case and resource pages by buyer question. Review CMS metadata, internal links and performance before growing the content library.
Explore technical SEOAgree required fields, ownership and delivery rules so a specialist question reaches the right person.
Explore connected workflowsBuild consistent templates for guides, research and resources, with clear editing responsibilities.
Explore website supportAgree what buyers, users and technical reviewers need to understand before requesting a demo.
Review real product explanations, evidence and resources alongside the enquiry journey.
Test old links, mobile layouts and enquiry destinations before handing over the CMS.
Two practical resources to help shape your brief.
I’m based in London and work remotely with your team. We use a shared brief, working previews and agreed review points, with one direct contact for design and development.
Yes. We can give buyers and technical reviewers separate routes through the same product, with reusable pages for use cases, evidence and practical requirements.
I can inventory existing URLs, map content into the new CMS and implement redirects where URLs change. We test the important pages and links before launch.
Yes. I can audit crawlability, metadata, internal links and performance, then scope the implementation. Service content should answer real buyer questions; we use search and enquiry data to choose priorities.
Share your product website, the questions buyers ask and the content your team needs to publish.

.jpg)
