IOpartner.ch
Contact IOpartner
IOpartnerProject conversations ↗Your conversation and its contextEmail ussupport@iopartner.chAnother request →
EN
FRENDEIT

IOPARTNER / BESPOKE SYSTEMS

Systems that move your business forward.

A well-organised Microsoft 365 workspace. A payment that triggers the right next action. A portal that replaces scattered files. We build and connect tools around the way your business works.

Discuss your project ↗

01 / DELIVERY

What you actually receive.

The right tools depend on your organisation. These are possible engagements and their deliverables, rather than a software shopping list.

01↗

Microsoft 365 · Entra ID · Teams · SharePoint

Your team, in one workspace.

Structure or migrate your working environment, its data and access.

  • Organised workspaces and libraries, role-based permissions
  • Employee onboarding and offboarding procedures
  • Controlled migration, documentation and training
Discuss your project →
02↗

Stripe · APIs · CRM · automation

From payment to the next operation.

Connect sales to what follows: invoicing, access, production and customer tracking.

  • Checkout or subscriptions matched to your model
  • Verified webhooks, retries and error visibility
  • Reconciled refunds and payment states
Discuss your project →
03↗

Portals · roles · dashboards

Your business, in your application.

Build around your processes, for customers, partners or your team.

  • Defined journeys, data model and permissions
  • Application and integrations with existing tools
  • Acceptance testing, tracking and handover
Discuss your project →
04↗

Cloud · Docker · CI/CD · observability

Infrastructure you can operate.

Design or stabilise your technical foundation, from deployment to incident recovery.

  • Documented architecture, environments and access
  • Configured deployments, monitoring and alerts
  • Backup, restore and handover procedures
Discuss your project →

IOPARTNER / COMMITMENT

A major investment deserves a clear framework.

For a CHF 200,000+ project, software alone is not enough. These points belong in the agreed scope and contract, with evidence of acceptance at each stage.

01

Invest in stages. Keep control.

A discovery phase, costed milestones, demonstrations and approval before the next stage. Scope changes require an explicit agreement.

Scope · budget · decisions
02

Your access. Your data. Your independence.

Production accounts in your organisation’s name where possible, documented permissions and agreed code handover. Licences, dependencies and export options are made explicit.

Ownership · access · exit plan
03

Prepare for the day something breaks.

Define risks, access, backups and recovery. Plan a rehearsed migration and rollback; agree support response times and service levels separately.

Security · recovery · continuity
04

Accept an outcome, not a promise.

Agree useful measures: time saved, reliability of a workflow or team adoption. Test against real scenarios and hand over documentation and training.

Acceptance criteria · knowledge transfer
Scope my investment ↗

02 / FIT

Technology follows the need.

Microsoft 365, Google Workspace, Stripe, Supabase, Vercel, Azure, Docker, CRM tools and existing APIs: we assess what fits your context, including keeping and simplifying what you already use.

IOPARTNER / BESPOKE PROJECT JOURNEY

Your project, from the first conversation to handover.

At every stage: what moves forward, what we need from you and the decision to prepare together.

  1. Understand the need
    Customer experience
    Explain goals, users, constraints and success measures.
    Next agreed step
    Agree who decides and what must be investigated.
    Evidence to keep
    Dated discovery summary, stakeholders and open questions.
  2. Define scope and proposal
    Customer experience
    Review deliverables, exclusions, options, budget and dependencies.
    Next agreed step
    Review the versioned proposal and acceptance criteria together.
    Evidence to keep
    Proposal version, estimate assumptions, risks and measurable acceptance criteria.
  3. Explicit agreement
    Customer experience
    Approve only a clear proposal through the agreed acceptance channel.
    Next agreed step
    Check the authorised signatory and record the accepted version.
    Evidence to keep
    Acceptance identity, time, exact version and agreed terms.
  4. Deposit and financial readiness
    Customer experience
    Receive the agreed invoice and payment instructions.
    Next agreed step
    Finance verifies payment or an approved credit arrangement before a gated start.
    Evidence to keep
    Invoice reference, verified payment state and approved start conditions.
  5. Kick off together
    Customer experience
    Meet the delivery team and agree access, content and communications.
    Next agreed step
    Confirm responsibilities, dependencies and the baseline plan.
    Evidence to keep
    Kickoff notes, named owners, access checklist and communication cadence.
  6. Build and review
    Customer experience
    See working demonstrations and raise questions against agreed scope.
    Next agreed step
    Agree the next increment and review changes before implementation.
    Evidence to keep
    Demo notes, decisions, change requests, tests and current risks.
  7. Test and accept
    Customer experience
    Test the agreed scenarios and record defects or acceptance explicitly.
    Next agreed step
    Resolve blocking defects and request a version-specific decision.
    Evidence to keep
    Test environment/version, results, defect list and explicit acceptance record.
  8. Prepare and launch
    Customer experience
    Review readiness, service interruption and the fallback plan.
    Next agreed step
    Obtain the agreed go/no-go decision before the controlled release.
    Evidence to keep
    Release checklist, backups, rollback rehearsal, monitoring and authorised decision.
  9. Hand over
    Customer experience
    Receive agreed access, documents, training and outstanding-item details.
    Next agreed step
    Verify recipients, ownership and remaining responsibilities.
    Evidence to keep
    Handover inventory, secure access receipt, training record and open-item owners.
  10. Operate and support
    Customer experience
    Know how to report an issue and which support terms apply.
    Next agreed step
    Triage impact against the agreed support arrangement and give the next update.
    Evidence to keep
    Incident timeline, relevant support terms, resolution evidence and follow-up.
  11. Exit or transition
    Customer experience
    Receive the agreed export and transition plan when the engagement ends.
    Next agreed step
    Agree export checks, access removal, retention and unresolved obligations.
    Evidence to keep
    Export verification, licence inventory, revocation record and approved retention plan.

When the project changes.

A new request along the way

We distinguish a correction within the agreed scope from a new request. Effects on price, timing and approvals are clarified before a decision.

A decision or access is missing

The blocker, its owner and the next action are identified. Affected dates are reviewed with you; a status does not replace confirmation.

An incident or sensitive matter

Describe the impact and who is affected. Do not send passwords or sensitive data in an ordinary message. We agree an appropriate channel and response with you.

After go-live

Warranty scope, maintenance, changes and support are defined in the project agreement. A support message does not commit to work or a response time that has not been agreed.

IOPARTNER / REFERENCES & METHOD

Work you can inspect. A clear way forward.

Existing projects, what they enable today and the documents we can prepare for yours. Unmeasured commercial outcomes are not presented as proven results.

01Delivered website · local services

Lausanne Déménagement

The need
Present a local service business and guide visitors towards a quote request.
What we built
Service presentation, mobile navigation and a contact journey for describing a request.
What you can inspect
A public website and an enquiry route accessible from the service pages.
Scope of this reference
This reference demonstrates the delivered website. No revenue increase or enquiry volume is claimed without measurement.
Visit the website ↗
02Delivered website · beauty

Ongles Gel

The need
Show the salon’s work and provide a direct way to get in touch.
What we built
Services, a work gallery, location and WhatsApp contact.
What you can inspect
Visitors can browse the work and open a conversation from the website.
Scope of this reference
The WhatsApp contact route is visible; it is not evidence of a confirmed appointment or increased bookings.
Visit the website ↗
03Our own product · business workflow

The IOpartner platform

The need
Connect customer requests, website purchases, production, approval and a partner programme.
What we built
Customer, partner and operator areas; referral attribution; payment, revision and content-approval tracking.
What you can inspect
Journeys were exercised in a hosted test environment through controlled website publication.
Scope of this reference
An internal product, not a client commission. Automatic publication remains paused and partner bank transfers are not automated. This case does not demonstrate real sales volume.
04Delivered website · private experiences

Lac Léman Experience

The need
Present experiences around Lake Geneva and collect context for a tailored enquiry.
What we built
Visual identity, experience presentation, practical information and a contact journey.
What you can inspect
A public website where visitors can explore experiences and prepare an enquiry.
Scope of this reference
This reference concerns the website and enquiry journey, not booking volumes, supplier availability or measured revenue.
Visit the website ↗
05Our product · in development

IC Immobilier

The need
Build a searchable property portal with favourites and listing management.
What we built
First implementation of search, listings, advertiser workspace, moderation and payment logic.
What you can inspect
Code and isolated checks covering filters, access controls, payment attribution and publication conditions.
Scope of this reference
Not launched: hosted payment journey still to verify, database changes not deployed to production and live payments disabled. Illustrations are not available properties.

IOPARTNER / DELIVERY KIT

Inspect the documents before entrusting us with the project.

Illustrative example: connecting a payment to a customer workspace. These documents show the level of detail we work towards; they are neither a quote nor a promise of results.

SAMPLE DELIVERABLE / 01

Scoping note

A decision, a boundary and measurable acceptance criteria.

Objective

  • After confirmed payment, give the right customer access to the right project without repeated manual intervention.

Proposed scope

  • One product, a CHF payment and one customer role; signed-event receipt, project creation and secure access recovery.
  • Excluded: historical migration, full accounting, third-party payouts and permanent support.

Decisions and dependencies

  • Confirm production accounts, the business owner, required data, budget, licences and retention arrangements.
  • Define refunds, failure handling and change requests before estimating.

Measurement to establish

  • Record current handling time and errors before the project; then agree a target and comparison method. No numerical saving is assumed.
Download the text template ↓
SAMPLE DELIVERABLE / 02

Acceptance plan

Observable scenarios instead of “it should work”.

Payment and repetition

  • One confirmed test payment creates exactly one project. Replaying the same event creates no duplicate or second entitlement.
  • An incomplete or failed payment grants no access.

Access and privacy

  • Customer A can access their project but cannot open customer B’s project, even with its identifier.
  • Expired or reused links are rejected; recovery does not reveal whether another address has an account.

Recorded acceptance

  • For each scenario: expected result, observed result, date, environment and evidence. Classify blocking and non-blocking issues.
  • The designated owner explicitly accepts the demonstrated version. Significant fixes require verification again.
Download the text template ↓
SAMPLE DELIVERABLE / 03

Handover pack

Operate, understand and recover the system.

Access and architecture

  • Inventory of services, owners, permissions and recurring costs. Secrets stay in a secure manager, never in the document.
  • Data and integration diagram, environments and deployment procedure.

Incident and recovery

  • Identify the affected service, preserve evidence and pause risky actions where needed. Inform the agreed contact.
  • Document backups, restoration rehearsal, rollback and checks after recovery.

After delivery

  • Support channel, covered hours, contacts, response times and follow-up duration must be completed in the proposal.
  • Distinguish a deviation from the accepted scope, maintenance and a new feature.
Download the text template ↓

IOPARTNER / PROJECT AGREEMENT

Know what you agree to. Know what you accept.

This framework informs each bespoke project proposal. Applicable amounts, dates and commitments are those in the document we agree together.

  1. 01
    Before commitment

    Written proposal

    Objective, deliverables, exclusions, dependencies, budget, payment schedule, licences and acceptance criteria. Assumptions remain visible.

  2. 02
    Before implementation

    Scope approval

    An owner on each side confirms the proposal and prerequisites. Significant changes state their cost and schedule impact before agreement.

  3. 03
    At each milestone

    Demonstration & acceptance

    We present an identified version and the agreed scenario results. Issues are recorded; acceptance is explicit, never inferred from silence.

  4. 04
    Before go-live

    Handover & follow-up

    Agreed access, documentation and training are handed over; support contacts and arrangements are confirmed. Go-live and rollback steps are agreed.

04 / YOUR PROJECT

Your project starts here.

Describe the outcome you need and the tools already in place. We will get back to you to define the right first step.

Book a technical session ↗

Do not submit passwords or confidential data in this form.