Zürich · For Swiss trust-administration teams
Trust onboarding. Your team decides.
Test one preparation workflow against your own checklist. Keep a prototype your team can rerun with agreed input formats, inspect and export before deciding on production use.
CHF 4,900 · One workflow · Two scheduled build days · About four hours from your team.
See scope and handover ↓01 · Client Onboarding Pilot
One trust-onboarding preparation task, built around your checklist. This pilot covers a manually operated prototype; live system connections and production use are separate decisions.
CHF 4,900
Fixed pilot fee. Any applicable VAT and payment milestones are confirmed in the written quote.
Agreed synthetic records in the specified formats, your checklist and a named reviewer.
Manually load another case in those formats. Inspect a source-linked review file, open exceptions and an editable client-update draft. Export the prepared pack.
Runnable workflow files and configuration in your account, operating instructions, handover, actual pilot test results and a written go/no-go recommendation with implementation and running-cost estimates. Assumptions and unknowns stay explicit.
We configure the agreed prototype environment in your account. You arrange account access and billing approvals. Scope, formats, prerequisites, dates and required third-party costs are agreed before the build starts.
Request a 15-minute pilot call02 · Try a trust-mandate example
A proposed contact for a fictional trust mandate has a missing address record and different names in two sources. Add the address; the name conflict must stay open.
Contact-record subset only. Scripted synthetic interaction, not a live AI run or a full trustee onboarding checklist. Nothing uploaded or sent.
01 · Incoming records
Alex Example
1 Example Street, Sample City
This sample is ready to add. It is not in the file yet.
02 · Prepared file
Address record missing. File remains incomplete.
Name conflict: Alex Example in ID-01; Alexis Example in CP-01. Human clarification required.
Next action: request the address record.
03 · Client update
Add the sample record to update this draft and unlock editing.
Includes all three source records, updated packet and your edited draft. Plain text.
Your team keeps the decisions. Adding a record changes this example checklist. A person still reviews the file and approves any message. No client acceptance or compliance clearance.
03 · Mandatory checks
Agree the cases and pass criteria before building. These proposed checks become the written acceptance list for your scope.
Your owner runs an additional synthetic case in the agreed formats, beyond the build examples, and exports the outputs.
Prepared facts cite sources. Missing records and conflicting details remain visible until a person resolves them.
Adding a record updates the same file and draft. Repeated actions do not overwrite a person's wording or silently clear another exception.
No message is sent and no client is accepted automatically. The named reviewer decides what happens next.
Your owner can follow the runbook in your account. You receive the test record, open limitations and cost estimates for any next phase.
No acceptance or final payment until mandatory checks pass. One correction round is included. If a mandatory check still fails, the pilot stops unaccepted and the final balance is not due. We document the failure; further work requires a new written agreement. Optional improvements are separate from mandatory defects.
04 · Before you commit
The prototype accepts manually supplied records in the formats and document types agreed in scope. Your team can rerun it on further synthetic cases, inspect the review file and exceptions, edit the draft and export. New formats, live inbox/CRM connections, real-client processing and production rollout need a separate scope.
One owner, your checklist, agreed synthetic inputs and access to your account. We configure the agreed prototype and provide operating instructions. Your owner arranges account permissions and billing approvals. Plan about four hours for scoping, output review and handover; prerequisites and dates are confirmed before the two build days begin.
No upload is required on this page. Pilot tests use synthetic records. Before building, the written scope identifies the proposed services, processing locations, access and retention settings, and separate licence, hosting and model-usage charges. You own the delivered workflow and configuration; third-party licences keep their own terms. Real client data requires a separate agreement before access.
You receive the pilot's actual inputs, outputs and pass/fail record, including the fresh case run by your owner, plus limitations and a written recommendation on whether to proceed. Implementation and recurring-cost estimates distinguish assumptions from quotes. The public example is scripted and synthetic; it is not customer proof or a measured savings claim. You can stop after the pilot without a follow-on engagement.
05 · Your next step
Speak directly with Tobias Temmen. Bring one trust-onboarding bottleneck. We check fit, then prepare a written scope and quote before you commit to CHF 4,900.
Opens an email draft to request a call. Nothing is booked or sent automatically.
Create and review it using the optional tools below before including it.
Optional · Your brief
Choose one bottleneck to get a proposed first output, a human review step and a test to run. Download your planning brief immediately. No booking or email required.
One choice is enough. Owner and workload figures are optional.
Your first result · Planning brief
Planning suggestion, not a working integration. Changes above update this brief.
Add workload assumptions (optional) ↓Choose a bottleneck above. Your brief will include the proposed preparation steps, human responsibilities and any workload assumptions you enter.
Optional · Your workload
Optional: add workload assumptions to your brief. Results update as you type. Unknown future effort can stay unknown.
Net annual hours released
Enter your workload and a scenario to see what your assumptions imply.
Time valued at staff cost is not cash saved. No revenue, headcount, calendar-speed or ROI prediction.
Include these assumptions in my brief ↓