Skip to content
Frihet
Frihet Studio

Get Frihet configured for the way you work.

Quickstart covers setup, 3 available integrations, 5 automations, a dashboard, migration, and a handover session. We confirm compatibility before work starts.

Quickstart scope: setup + 3 available integrations + 5 automations + dashboard + reviewed migration + handover.

Check my fitPick a time
Illustrative example
app.frihet.io
INCOME
2.125 €
this month
EXPENSES
110 €
this month
PROFIT
1.750 €
this month
Revenue Goal
27%
Tax view
Forecast
Ready
3 integrations · 5 automations

FIT BEFORE IMPLEMENTATION

First, we confirm whether Quickstart is the right path.

We do not start changes or promise a timeline until we have reviewed the integrations, source data, and outcome you need.

It fits when

  • You want the published Quickstart scope.
  • Your tools are listed as available and are compatible with your use case.
  • You can provide access, sample exports, and the decisions required.

We need to review another path when

  • You depend on an integration that is blocked, paused, or not implemented.
  • You need custom development outside the Quickstart scope.
  • You need a deadline or support arrangement that has not been agreed.

PUBLISHED SCOPE

Quickstart

Six concrete deliverables, subject to compatibility, source formats, and client validation.

Initial setup

We prepare Frihet's base structure according to the scope we have validated.

3 available integrations

We configure up to three live catalog integrations that are compatible with your workflow.

5 available automations

We agree and configure up to five automations supported by the product and scope.

Operational dashboard

We prepare a working dashboard using the available views that matter to your case.

Reviewed migration

We review a sample and migrate the agreed data when its format and quality allow it.

Handoff session

We validate the setup with you and explain how to continue with the delivered system.

How it works

  1. Fit review

    We review tools, data, dependencies, and the outcome you want to leave working.

  2. Scope and implementation

    We confirm inputs, boundaries, and responsibilities, then configure what was agreed.

  3. Validation and handover

    We review the result with you, resolve outstanding in-scope items, and hand it over.

Let's review the fit.

Share your tools, source data, and the outcome you want to leave working.

We do not start changes until scope and dependencies are confirmed.

Prefer to pick a time directly? See availability

What we need and where the boundaries are.

We validate these dependencies before work starts. If one does not fit, you will know before we confirm the implementation.

See integrations See features Review a migration
  • 01 Integrations must be live in the catalog and compatible with your configuration.
  • 02 We need the agreed access and exports; never share passwords through the form.
  • 03 Decisions and final validation require a responsible person on your side.
  • 04 Migration depends on the source format, data quality, and a representative sample.
  • 05 Timeline, extras, and any post-handover support are agreed after the case review.

Questions before you decide

What exactly does Quickstart include?

Initial setup, 3 available integrations, 5 automations, an operational dashboard, reviewed migration, and a handover session, always subject to compatibility and the agreed scope.

Does any integration qualify?

No. We only confirm integrations that are live in the catalog and compatible with your case. Blocked, paused, or not-implemented integrations are outside the scope.

What data can you migrate?

We determine that after reviewing a sample. The scope depends on format, quality, and its match with Frihet's available import paths.

What do you need from me?

A clear outcome, secure access to the agreed tools, sample exports, and someone who can make decisions and validate the handover.

How long does it take and what support is included?

We confirm the timeline after reviewing dependencies and scope. The published pack ends with the handover session; any additional support is agreed separately.