One campaign team, several teams to coordinate or a large organisation: identify the features your project needs before discussing a budget.
Résonance is in preparation. These plans describe the proposed way of working. Budgets are discussed on request; subscriptions are not open on this website.
01
Studio
For one organisation and its campaign team
Budget on request
Based on your team, its campaigns and the tools you use.
Structure the work, from brief to reporting.
Bring a campaign’s working material into one shared dossier. Prepare the formats, organise review and hand over a version whose sources and limitations are clear to everyone.
A shared framework for your organisation’s campaigns.
A library of sources, facts and reference wording.
Content formats developed from the same brief.
Review and approval of the agreed version.
Documented exports and a view of available results.
Onboarding and a structure for the first campaigns.
Your priority: replace scattered documents with a shared campaign dossier.
02
Integral
For several teams, clients or entities
Budget on request
Based on the teams to coordinate and the responsibilities they share.
Coordinate campaigns across teams.
Give teams a common point of reference while keeping responsibilities clear. Follow dossiers, versions requiring changes and outstanding approvals across your organisation or client portfolio.
The Studio foundation, with oversight across dossiers.
Workspaces and responsibilities by team or entity.
Agency and client collaboration within an agreed mandate.
Shared libraries and controlled local adaptations.
Your priority: keep work consistent when several teams or organisations contribute.
03
Enterprise
For organisations with specific requirements
Budget on request
Based on your organisations, tools to connect and training needs.
Define a deployment around your organisation.
Identify the organisations involved, the teams that need to work together and the tools to keep. Then agree who can access information, how to transfer existing files and how to train the teams.
Entity structure and access governance.
Data scope and flows between systems.
Bespoke integrations to assess and price.
Documented operating requirements and responsibilities.
Your priority: fit the product into a complex organisation with explicit conditions.
To discuss a budget, describe a campaign, the people working on it, your current tools and any files to transfer. We can then distinguish the future subscription, setup, training and any development work required. Prices, usage limits and contract terms must be specified before any commitment.
The scope in detail
Compare how the work is organised.
This comparison presents the features planned for all three options. The choice will depend on the number of teams, how they work together and the tools to connect. Available features will be specified before any commercial proposal.
Starting point+
Studio
One organisation and its campaign team
Integral
Several teams, entities or clients to coordinate
Enterprise
A group and its deployment requirements
Campaign dossier+
Studio
Brief, schedule, sources, content and decisions
Integral
The same dossier, with oversight across teams
Enterprise
The same foundation, structured around the agreed scope
Reference library+
Studio
The organisation’s facts, documents and wording
Integral
Shared references and team-level adaptations
Enterprise
Library governance across entities
Formats and versions+
Studio
Formats from one brief, corrections and history
Integral
Version coordination across teams
Enterprise
Production workflows specified in the scope
Review and approval+
Studio
Explicit responsibilities and an agreed version
Integral
Successive approvals across teams and partners
Enterprise
Workflows and responsibilities defined at deployment
Changed source+
Studio
Identify content and decisions requiring review
Integral
Coordinate changes across affected dossiers
Enterprise
Define dependencies across entities
Agency and client work+
Studio
A dossier within the organisation’s context
Integral
Separate mandates, workspaces and client access
Enterprise
An agreed delegation model for the group
Handover and reporting+
Studio
Documented exports, confirmed returns and missing data
Integral
Oversight of handovers and reporting across dossiers
Enterprise
Flows and reporting views agreed with the teams
Existing tools+
Studio
Import and export scope defined at the start
Integral
Coordination of the flows required for deployment
Enterprise
Bespoke integrations assessed and priced
Onboarding+
Studio
A structured start and first campaigns
Integral
Deployment and training across several teams
Enterprise
Adoption by entity and agreed responsibilities
Rights and exit+
Studio
Access, restrictions and data retrieval
Integral
The same foundation, with defined delegation
Enterprise
The same foundation, with governance across entities
Capacity and usage+
Studio
Users, data and usage sized for the scope
Integral
Allowances allocated across teams and workspaces
Enterprise
Allowances and conditions specified in the contract
Essential features for every team.
A campaign dossier connects the objective, sources, content, reviewers and agreed version. Keep qualifications visible through handover, then distinguish confirmed results from what remains unknown.
Campaign brief, schedule and responsibilities.
Reference facts, dated documents and shared vocabulary.
Drafts, formats, corrections and versions.
Review, approval and reassessment when a source changes.
Handover dossier and documented reporting.
Access rights, restrictions and data retrieval.
Advertising space, printing, postage and tools that send your messages are billed separately. If existing files are difficult to transfer or another tool needs connecting, that work is described and priced separately.
Studio is intended for one organisation and its campaign team. Integral adds coordination across several teams, clients or establishments. Enterprise provides a way to discuss a more complex organisation and its particular needs. Start with a concrete campaign: who prepares the texts, who reviews them and which tools those people use.
Why are budgets discussed on request?
The software is in preparation and prices have not been set. A budget should reflect the available features, the people using them and the setup work required. We discuss those details around your project, then specify amounts and terms before any commitment. This page does not let you subscribe or pay for a subscription.
Why distinguish Studio and Integral?
One team can share its documents and texts in a common dossier. Several teams also need to know who can access each dossier, who should review a text and which changes affect them. Studio and Integral distinguish these two ways of working; the difference must reflect features that are actually available.
Do I need a contact list?
No. Project documents are enough to prepare a public page, a speech or answers to frequently asked questions. If the campaign involves messages addressed to people, their contact details and preferences also need to be reviewed. The need therefore depends on the work to do, not only on the size of a file.
Which formats are planned?
The project includes preparing several texts from the same information: a public page, an email, a letter or a brief for a local team. Length and tone may change while dates, figures and information awaiting confirmation remain consistent. Preparing those texts and publishing them through your tools are separate steps.
How should we plan work with an agency?
Identify the people in your organisation and the agency who need to contribute. Specify which documents they may read, which texts they prepare and who gives approval. These details help define the access required without mixing dossiers belonging to different clients.
Are my existing tools included in the budget?
List the tools you use to send emails, publish pages or track donations. The proposal must specify how to pass texts to them and retrieve useful information: through files or a direct connection, if available. Their subscriptions, advertising space, printing and postage are separate expenses to plan for.
Which quantities should we specify?
The number of people using the software, campaigns prepared, documents kept and writing requests help estimate the need. If contacts are used, their number matters too. Limits and the price of any increase must be known before you accept them; this presentation promises no unlimited usage.
What is an AI writing request?
It is a request for a draft or another wording, such as a shorter version of an email. The number of people receiving that email is a separate measure. Counting and billing rules must be explained before use.
What will onboarding involve?
It is planned to help teams use the software: organise their documents, decide who prepares and reviews texts, then work on a first campaign. Transferring complex files or creating a connection with another tool requires separate work, to be described and priced if needed.
Is a commission on donations planned?
The proposed model is a software subscription without commission on donations. Final commercial terms will be specified before subscriptions open. A fundraising total alone cannot measure the software’s effect: costs and other campaign activities also need to be considered.
How should we prepare a complete budget?
Describe a campaign, the people involved, your tools and any files to transfer. Then separate the future subscription, setup, training and external expenses such as email delivery or printing. Taxes, commitment, payment, renewal and exit terms must appear in the proposal before any agreement.
Your next campaign starts here
Give your ideas a next step.
Explore the product through a concrete case, compare plans and prepare your rollout with the right questions.
