Amass Services
From first use case to production deployment
Use Amass directly, integrate our API, or engage our team to design, build and operate a scientific intelligence workflow in your environment.
From training and technical discovery to full forward-deployed implementation, we provide the level of support needed to get your team into production.
How do we use Amass?
Choose how Amass fits into your organisation
Product access is the first question — the level of support you need is the second. Start with where Amass should live.
Amass App
A ready-to-use scientific research workspace for teams conducting searches, analyses, monitoring and evidence synthesis.
Best for: Teams that want to start immediately without building an integration.
Amass API
Programmatic access to Amass data, search, retrieval and scientific intelligence capabilities.
Best for: Product teams and internal engineering teams building their own workflows, agents or applications.
Embedded Amass
Amass integrated into an internal platform, customer-facing product or operational workflow.
Best for: Organisations that want Amass to become part of an existing product or infrastructure layer.
The two questions, combined
Access is one axis, support is the other. Tap any pairing to see what the engagement looks like.
We build the integration — data mapping, auth, testing — and hand over documented, running code.
How does Amass help us succeed?
Choose the level of support you need
Three engagement levels — from getting your team fluent to an embedded delivery partner. Combined and scoped per engagement, not sold as rigid packages.
Enable
Get your team ready to use Amass effectively.
- Stakeholder and use-case discovery
- Team onboarding
- Role-specific training
- Prompt and workflow development
- API and architecture workshops
- Governance and usage recommendations
- Office hours and adoption support
What's included (7)
- Stakeholder and use-case discovery
- Team onboarding
- Role-specific training
- Prompt and workflow development
- API and architecture workshops
- Governance and usage recommendations
- Office hours and adoption support
Typical outcome: A trained team, prioritised use cases and a clear adoption plan.
Implement
Move a defined use case into a working production workflow.
- Technical discovery and solution design
- Data-source and workflow mapping
- API integration
- Authentication and access configuration
- Internal data integration
- Application or agent implementation
- Testing, evaluation and acceptance criteria
- Deployment support
- Technical documentation and handover
What's included (9)
- Technical discovery and solution design
- Data-source and workflow mapping
- API integration
- Authentication and access configuration
- Internal data integration
- Application or agent implementation
- Testing, evaluation and acceptance criteria
- Deployment support
- Technical documentation and handover
Typical outcome: A deployed workflow, integration or application that your team can own and operate.
Forward Deploy
EmbeddedEngage Amass as an embedded delivery partner.
- Embedded forward-deployed engineer or team
- Product and workflow design
- Custom agents, applications and interfaces
- Scientific evaluation frameworks
- Data architecture and ontology work
- Production deployment
- Monitoring and optimisation
- Ongoing roadmap and operational ownership
- Training and internal capability transfer
What's included (9)
- Embedded forward-deployed engineer or team
- Product and workflow design
- Custom agents, applications and interfaces
- Scientific evaluation frameworks
- Data architecture and ontology work
- Production deployment
- Monitoring and optimisation
- Ongoing roadmap and operational ownership
- Training and internal capability transfer
Typical outcome: A production system delivered and evolved jointly with Amass.
These are engagement levels, not rigid packages — they combine and scope in an order form or statement of work. Enablement may be included in larger subscriptions; implementation and forward-deployed work are normally scoped separately.
The strategic engagement
Build your own *Core
Turn your organisation's knowledge into a dedicated intelligence layer.
An Amass *Core combines selected external data, internal knowledge, scientific workflows and domain-specific logic into a dedicated intelligence environment — designed, built and deployed with your scientific, product and technical teams.
What goes in
What comes out
Company Core
An intelligence layer across internal research, assets, programmes and external evidence.
Therapeutic Area Core
Structured knowledge for a disease area, modality or biological domain.
Asset Core
A continuously updated view of a target, molecule, programme or portfolio.
Regulatory Core
Internal and external regulatory knowledge organised around products and markets.
Customer Core
A scientific intelligence capability embedded into a platform or customer-facing product.
Content Core
Controlled access to proprietary content through AI-native search, workflows and applications.
Possible *Core types (6)
Company Core
An intelligence layer across internal research, assets, programmes and external evidence.
Therapeutic Area Core
Structured knowledge for a disease area, modality or biological domain.
Asset Core
A continuously updated view of a target, molecule, programme or portfolio.
Regulatory Core
Internal and external regulatory knowledge organised around products and markets.
Customer Core
A scientific intelligence capability embedded into a platform or customer-facing product.
Content Core
Controlled access to proprietary content through AI-native search, workflows and applications.
Core engagement options
Core Discovery
- Use-case and stakeholder workshops
- Data and systems assessment
- Initial domain and workflow mapping
- Architecture recommendation
- Pilot and rollout plan
What's included (5)
- Use-case and stakeholder workshops
- Data and systems assessment
- Initial domain and workflow mapping
- Architecture recommendation
- Pilot and rollout plan
Outcome: A clear *Core specification and implementation roadmap.
Core Pilot
- A scoped set of internal and external sources
- Initial ontology or entity model
- One or more priority workflows
- User interface or API access
- Evaluation with representative users
What's included (5)
- A scoped set of internal and external sources
- Initial ontology or entity model
- One or more priority workflows
- User interface or API access
- Evaluation with representative users
Outcome: A functioning *Core pilot with documented performance and production requirements.
Production Core
- Production data integrations
- Identity, access and governance
- Custom workflows and applications
- Continuous data updates
- Monitoring and evaluation
- Training and operational support
- Joint roadmap
What's included (7)
- Production data integrations
- Identity, access and governance
- Custom workflows and applications
- Continuous data updates
- Monitoring and evaluation
- Training and operational support
- Joint roadmap
Outcome: An organisation-specific intelligence capability operated independently or jointly with Amass.
What the work is made of
Services across the lifecycle
Discovery & design
- Executive and stakeholder workshops
- Use-case identification and prioritisation
- Technical feasibility
- Data and systems mapping
- Success metrics
- Security and deployment planning
Services (6)
- Executive and stakeholder workshops
- Use-case identification and prioritisation
- Technical feasibility
- Data and systems mapping
- Success metrics
- Security and deployment planning
Training & enablement
- User onboarding
- Research workflow training
- Developer and API training
- Team-specific playbooks
- Train-the-trainer programmes
- Recurring office hours
Services (6)
- User onboarding
- Research workflow training
- Developer and API training
- Team-specific playbooks
- Train-the-trainer programmes
- Recurring office hours
Implementation
- API and SDK integration
- Internal data connection
- SSO and access management
- Workflow and agent development
- Custom application development
- Evaluation, testing and deployment
Services (6)
- API and SDK integration
- Internal data connection
- SSO and access management
- Workflow and agent development
- Custom application development
- Evaluation, testing and deployment
Operations & optimisation
- Monitoring and incident support
- Usage and quality reviews
- Workflow optimisation
- New data-source activation
- Model and retrieval tuning
- Roadmap reviews and ongoing engineering capacity
Services (6)
- Monitoring and incident support
- Usage and quality reviews
- Workflow optimisation
- New data-source activation
- Model and retrieval tuning
- Roadmap reviews and ongoing engineering capacity
The delivery process
How an engagement works
Start where you need to. Most engagements begin with a scoped pilot, but customers with an established specification can enter later in the process. Each phase ends in named, artifact-shaped deliverables — the same ones your statement of work will cite.
Who you work with
Forward-deployed engineer
Ships in your repo and your environment — integrations, agents, pipelines.
Scientific lead
Owns evaluation frameworks and domain modelling with your researchers.
Engagement lead
One accountable owner for scope, phases and deliverables — Align to Operate.
Everything runs on enterprise cloud infrastructure in EU regions, through your IT and security review — see how we handle security →
What this looks like in practice
Example engagements
Six shapes an engagement takes — each with the kind of artifact it delivers and where it sits in the vocabulary above.
After the build
Support designed around your deployment
Each engagement level pairs with a support model — same vocabulary, no second menu to learn.
Standard adoption
with Enable
Typically available with team and enterprise subscriptions.
- Structured onboarding
- Standard technical support
- Documentation and implementation guidance
- Initial team training
- Periodic adoption reviews
Included (5)
- Structured onboarding
- Standard technical support
- Documentation and implementation guidance
- Initial team training
- Periodic adoption reviews
Guided implementation
with Implement
For customers deploying a defined integration or workflow.
- Named implementation lead
- Discovery and architecture sessions
- Configured implementation plan
- Developer support
- Testing and launch support
- Team training and handover
Included (6)
- Named implementation lead
- Discovery and architecture sessions
- Configured implementation plan
- Developer support
- Testing and launch support
- Team training and handover
Strategic deployment
with Forward Deploy
For larger, multi-team or business-critical programmes.
- Dedicated engagement lead
- Forward-deployed engineering capacity
- Custom development and integration
- Joint roadmap and governance
- Ongoing production support
- Recurring scientific and technical reviews
Included (6)
- Dedicated engagement lead
- Forward-deployed engineering capacity
- Custom development and integration
- Joint roadmap and governance
- Ongoing production support
- Recurring scientific and technical reviews
The appropriate service level is defined in the order form or statement of work and depends on scope, complexity and the level of ongoing ownership required.
Start with the outcome
Tell us what your team needs to deliver, where the workflow needs to live and how much implementation support you require — we'll recommend the starting point: enablement, a scoped implementation, a forward-deployed engagement or a custom *Core.