Defined work, billed by the hour.

Scientific data work carries uncertainty that a fixed quote can hide rather than remove. We inspect a representative sample, estimate the likely hours and state the assumptions. Small phases can use a hard spending cap. Larger builds are divided into work packages.

The proposal records the hourly rate, expected range, cap where agreed, review points and outputs. Time logs are supplied with invoices.

Best for

A team with a concrete problem, existing material and uncertainty about the right first piece of work.

Typical time

2 to 4 hours

Inputs

• short problem statement;
• representative file or screenshots;
• current method or repository outline;
• deadline and intended use;
• data-access constraints.

Work

We review the material, identify the main technical risks and define a bounded first phase. This can include a short call, document review and written scope.

Output

• proposed technical question;
• required inputs;
• first-phase tasks;
• expected hours and assumptions;
• exclusions and decision point.

Billing

Hourly. A two-hour minimum may be applied where document review is required.

CTA

Request technical scoping

Best for

A pilot dataset, existing analysis or image/signal workflow that needs an independent technical inspection before more work is commissioned.

Typical time

12 to 30 hours

Work may include

• file and metadata audit;
• acquisition or annotation review;
• missingness, drift, artefact or batch analysis;
• reproduction of the current method;
• validation split review;
• code and dependency inspection;
• raw-to-result trace for selected examples.

Output

• findings report;
• prioritised failure list;
• annotated examples;
• recommended next phase;
• review call.

Billing

Hourly with an agreed cap. The review stops at the cap unless an extension is approved.

CTA

Scope a data and methods review

Best for

A defined scientific or engineering question that needs code, comparative analysis and a decision within one bounded phase.

Typical time

40 to 100 hours

Work may include

• signal or image quality model;
• preprocessing comparison;
• baseline and challenger models;
• grouped validation;
• confound and ablation tests;
• annotation sampling;
• event or object detection;
• uncertainty and failure analysis.

Output

• reproducible code;
• technical report or methods note;
• figures and tables;
• failed-case examples;
• recommendation based on the supplied data;
• handover session.

Billing

Hourly, usually split across two or three milestones. Each milestone has its own estimate and review.

CTA

Scope an analysis sprint

Best for

A recurring scientific workflow that needs tested ingestion, QC, analysis and reporting.

Typical structure

Phased implementation rather than one pre-data estimate

1. workflow and input review;
2. technical design;
3. first working path on representative data;
4. edge cases and QC;
5. documentation and handover.

Output

• source code and tests;
• schemas and configuration;
• automated QC;
• run logs or manifest;
• agreed deployment package;
• documentation and training.

Billing

Hourly by work package. Every package has an estimate, assumptions and acceptance review. Client delays or new input variants enter a revised estimate.

CTA

Discuss a pipeline implementation

Best for

A team with a maintained pipeline or continuing analysis backlog that does not justify a full-time hire.

Typical reservation

16 or 32 hours per month, agreed for an initial three-month period.

Suitable work

• bug fixes and dependency updates;
• new instrument or file variants;
• scheduled QC review;
• bounded analysis extensions;
• methods support;
• code review and handover support.

Operating boundary

Work is drawn from a named backlog. The reservation does not create a client job title, staff rota, line-management responsibility or open-ended availability.

Billing

Reserved hours are invoiced monthly under the agreed terms. Extra work requires written approval.

CTA

Discuss reserved support

A changed target, new modality, new deployment environment or undocumented file family can alter the work materially. We record the change, estimate it and wait for approval. The original cap remains intact until that approval is given.

The estimate assumes timely access to the agreed data, documentation, code and technical contact. Hours spent reconstructing missing acquisition details are still delivery hours. We flag the issue before consuming a material part of the cap.

The proposal identifies:

• client data and permitted access;
• controller and processor roles where personal data are involved;
• secure transfer or client-hosted execution;
• client-owned outputs;
• AmperieLabs background tools and reusable methods;
• retention and deletion;
• publication or publicity permissions.

Services cover research and engineering work. We do not provide diagnosis, treatment recommendations, regulatory approval or safety certification. Work that may form part of a medical device, clinical investigation or safety-critical system requires a separate scope, appropriate client governance and confirmed insurance cover.

Start with the smallest phase that can change the decision.

Describe the problem