Pricing

How ResearchGuru EDC Is Priced

Each study is quoted on its own scope. You receive a written scope of work, a delivery schedule and a quotation before any work starts.

A ten-item questionnaire at one site and a two-year, multi-site study with a participant diary are different amounts of work, so we don't publish a single price. This page explains what the quotation depends on, so you can estimate where your study sits and write a realistic budget line.

Request a quotation

What drives the quotation

Six things that determine the price

Pricing depends on the study's complexity, questionnaire/form length, required logic, number of users and sites, reporting requirements, support needs and expected duration.

Size of the eCRF

The number of forms and items, and how many visits or diary time points repeat them.

Logic and checks

Skip logic, calculations, edit checks, quotas, randomisation and safety notifications.

Sites, users and languages

How many sites and user roles need setting up, and how many approved translations are configured.

Participant-facing parts

eDiaries, consent pages, invitations and reminders add build and testing work.

Reporting and exports

Dashboards, tables, figures and listings, and standard exports such as CDISC.

Duration and support

How long data collection runs, and the level of support and documentation the study needs.

What the managed service covers

The quotation sets out what is included for your study. These are the usual components.

Build and activation

From approved documents to a live database.

  • Review of your study documents
  • eCRF programming and configuration
  • Internal quality control
  • Support for User Acceptance Testing
  • Activation and user set-up
Running the study

For the agreed duration of data collection.

  • Secure hosting and scheduled backups
  • Audit trail and role-based access
  • Technical support for your study team
  • Monitoring dashboards as agreed
  • Database closure and final data delivery

Changes requested after activation are assessed and quoted through the change-control process, so you see the cost and timeline before approving them.

Keeping the cost down

Four decisions that keep a study within budget

Most of the cost of a database is decided before programming starts. These are the choices that make the largest difference, whichever system you use.

Before the build

  • Approve the questionnaire/form first. Changes during programming are cheap; changes after activation go through change control.
  • Collect what the analysis needs. Every extra item is built, tested, completed by participants and cleaned.
  • Agree the outputs early. Knowing the tables and export format at the start shapes item codes and answer lists.
  • Name the testers. User Acceptance Testing moves quickly when the people and dates are agreed in advance.

Getting a quotation

From first message to a firm price

The review comes first. Nothing is built, and nothing is charged for the build, until you have accepted the scope.

Send your documents

A draft questionnaire/form and a protocol synopsis are enough to start. Tell us the number of sites, expected participants and target start date.

We review and ask questions

A senior researcher reads the documents and notes anything that affects the build, usually in a short call.

You receive the proposal

A clear scope of work, an estimated delivery schedule and a quotation, set out so that it can go into a grant application or a budget.

Frequently asked questions

Pricing: common questions

Something else? Get in touch and a senior researcher will answer.

A firm quotation needs the document review. If you describe the study, its length and the number of sites when you get in touch, we will tell you what else we need.

Yes. We can provide it in advance, with the scope described in terms a funder will recognise.

Amendments are handled as change requests. Each one is assessed, and its cost and timeline are agreed before the work is done.

The quotation states what is included for the agreed duration of data collection, so hosting, backups and support are set out in the scope from the start.

No. ResearchGuru is built for small studies as much as large ones.

You do. The final dataset is delivered in the agreed format, and retention and disposal follow the agreement.

Request a quotation

Send us your questionnaire/form and study requirements. We'll review the proposed structure and come back to you with:

Start your enquiry

Or email admin@edcstat.com · call +44 7484 816484

  • An initial database-build assessment
  • Any questions or recommendations
  • A proposed delivery schedule
  • A clear scope of work
  • A project quotation