Trace

Early-access pricing · Hypotheses, not a standing offer

Pay for a controlled outcome before you buy a platform.

Trace is testing whether product teams will fund the mapping and managed coordination behind one review-ready GDPR request case. Prices shown here are experimental presentations; application is free and no payment is taken online.

Apply for a pilot Understand implementation
Experiment assignmentPaid pilot first

Whether teams will pay for a concrete outcome before buying ongoing software. Your assignment is persistent, and plan interactions are recorded with the displayed amount. This is not personalised pricing.

Assigned early-access pricing presentation

Concrete first outcome

Concierge pilot

€1,500 one-time
One test or live request

Map up to three primary sources and prepare one review-ready case with a human review handoff.

  • Stack-readiness review
  • Up to three primary sources
  • One case pack
  • Implementation recommendation
Apply for a pilot

Accepted pilots only · terms agreed before payment

After a successful pilot

Annual

€3,490/ year
Pilot credit subject to approval

Maintain the mapped workflow for future requests after the pilot demonstrates fit.

  • Maintained source map
  • Managed case operations
  • Review handoff
  • Audit-package preparation
Discuss annual

Commercial hypothesis · credit is not automatic

No fake checkout. Selecting a route starts or links to an application. Initial pilots assume the customer supplies the authorised reviewer. Trace must confirm operational capacity, reviewer arrangements, security, scope, timing and terms before it can request payment or receive customer data.

What the fees are for

Mapping is the product before repetition is possible.

A generic workflow cannot know which user identifier links your billing system to support history or where a custom database stores attachments. Implementation makes that path explicit.

One-time implementation · Proposed scope

Build the first trustworthy path

  • Stack-readiness and request-intake review
  • Source, identifier and ownership mapping
  • Least-privilege or export-based access design
  • Test retrieval and gap discovery
  • First case configuration and hand-off design
Recurring service · Commercial hypothesis

Keep the path usable

  • Maintain the agreed source map
  • Coordinate accepted case preparation
  • Organise evidence and case metadata
  • Prepare response and exception drafts
  • Hand off a documented case for authorised review
Why not hide implementation inside the monthly fee?

The cost occurs before a repeatable workflow exists: understanding schemas, agreeing access, testing identifiers and exposing missing sources. Showing it separately makes the trade-off legible. The annual experiment asks whether buyers prefer committing for a year in exchange for having that work included.

Case-pack scope

The recurring outcome has a review boundary.

Actual deliverables are fixed in the accepted proposal. The table below describes the target structure, not a guarantee that every artefact is appropriate for every request.

Target case-pack contents
  • Case summary and request classification
  • Identity-verification status—not a universal identity decision
  • Agreed source inventory and retrieval notes
  • Available evidence package
  • Draft response and action checklist
  • Exception, third-party and missing-source flags
  • Timestamped activity record
Never implied by the listed price
  • Guaranteed legal compliance or case outcome
  • Automatic disclosure, redaction or erasure decisions
  • Unlimited systems, entities or request volume
  • Instant production connectors for every named tool
  • Named reviewer capacity unless contracted
  • Security certifications that have not been earned
  • Legal representation or regulator engagement
Scope may change with
More systemsMultiple entitiesCustom retentionComplex third-party dataProcurementSecurity review

A simple buying sequence

No contract before the work is credible.

  1. 01
    Apply with operating context

    Share company type, scale, request volume, pain and system names—never connector credentials or request data.

  2. 02
    Readiness is assessed

    Trace checks fit, scope, security expectations, access method and whether the required human capacity can genuinely be arranged.

  3. 03
    A written scope replaces the hypothesis

    Only an accepted proposal can define deliverables, timing, price, cancellation, data handling and reviewer responsibilities.

  4. 04
    Payment follows agreement

    No card details are collected as a proxy for intent. If Trace cannot deliver the scope, it should not charge for it.

Commercial questions

The details should be clearer than the discount.

Are these final, generally available prices?
No. They are controlled pricing hypotheses for an early-access managed service. The exact offer, scope and price only become real when Trace can issue and honour an accepted proposal.
Will I be charged when I apply?
No. There is no checkout on this website. An application does not create a contract, reserve capacity or authorise data processing. Payment can only follow accepted scope and pilot terms.
Why is there an implementation fee?
A request workflow is useful only when it knows where relevant data lives. The proposed implementation work covers source mapping, access design, test retrieval, exception discovery and the first case configuration.
What does the recurring fee cover?
The hypothesis is that recurring value comes from maintaining the source map and operating a repeatable case-preparation workflow. Volume, response coverage and reviewer involvement must be defined in the accepted scope; no unlimited service is implied.
Is qualified human compliance review included?
The initial pilot model assumes the customer supplies its authorised reviewer. Trace prepares the documented handoff; it does not include qualified compliance review by default. A Trace or partner review role exists only if an accepted proposal explicitly names the person, qualifications, capacity and boundary.
Why might implementation be included annually?
That is the annual-commitment hypothesis: a longer commercial relationship may justify absorbing upfront mapping work. The website is measuring preference, not making a standing contractual offer.
What makes a case more complex?
More systems, unfamiliar schemas, multiple entities, difficult identity matching, custom retention rules, security review, unusual delivery controls or extensive third-party information can change the work. Complexity is scoped before acceptance rather than hidden behind arbitrary limits.
Can a pilot fee be credited to an annual agreement?
Only where the final commercial proposal explicitly approves that credit. It is not automatic, and no annual agreement follows merely because a pilot is completed.

A controlled first request

Start with fit, scope and one concrete outcome.

Applying is free. No payment or data transfer is requested unless Trace can accept the pilot under an agreed operating and security boundary.

Start the pilot application See the sample case