From protocol to a complete recruitment campaign.
Acrova turns the protocol into structured recruitment work: study review, campaign generation, image direction, revision, and export. The product is still evolving, so the frontend is built to expose the flow clearly while the backend matures.
See it work
A clean run from study DNA to review-ready assets.
Upload protocol
Bring in the PDF and extract the study DNA, eligibility, and site context.
Review the study
Confirm the patient-facing facts before anything creative is generated.
Generate campaigns
Create ad copy, image briefs, validation, and export-ready versions.
Export and revise
Review outputs, tune variants, and push clean packages to the next step.
A clearer path than a generic dashboard.
The frontend should teach the user what happens next, which decisions matter, and where the agent flow is visible.
Upload protocol
Bring in the PDF and extract the study DNA, eligibility, and site context.
Review the study
Confirm the patient-facing facts before anything creative is generated.
Generate campaigns
Create ad copy, image briefs, validation, and export-ready versions.
Export and revise
Review outputs, tune variants, and push clean packages to the next step.
The app should feel like a product, not a workspace accident.
The best SaaS layouts make the next action obvious. The current frontend needs that same discipline: reduce noise, show the flow, and reserve detail for the right stage.
Before
A generic dashboard with no clear journey.
After
A staged flow that teaches the product.
What the flow should look like
Each stage should answer one question, then reveal the next.
Every team recruits differently. The layout should respect that.
A good SaaS homepage does not just explain features. It helps different buyers find themselves in the product.
Keep protocol facts, compliance, and brand integrity aligned across every recruitment touchpoint.
Run more studies without multiplying manual creative work or review overhead.
Stand up local recruitment materials with the right phone, location, and study language.
Offer a clearer, faster workflow for clinical recruitment without forcing generic ad templates.
The packaging can still move, but the hierarchy should already be there.
I would keep the pricing-style section because it anchors the narrative, but label it as a preview until the product model is final.
Launch
Best for single studies that need a clean, fast path to initial review.
Studio
For teams that want more control over copy, imagery, and revisions.
Partner
For longer-term programs that need more oversight and operational support.
Trust should be visible in the layout, not buried in a footer.
This product works best when the UI makes traceability, auditability, and careful review feel native to the experience.
Protocol traceability
Every claim should map back to the study facts and extracted DNA.
Audit visibility
Keep prompt, response, validation, and revision data visible while UAT evolves.
Data discipline
Build a product that is careful by default and avoids unnecessary sensitivity.
Build the homepage like the product deserves to be sold.
The marketing page now sets the tone. The next step is to align the product shell and UAT surfaces to the same standard.