Skip to Content
00 · Services



​​​​​​

Wir bauen Software.

Operations complete it.


Engineering is the core practice. Operations keep what we build alive in production. Advisory and governance sit alongside — embedded in delivery, not sold as separate workshops. One Swiss-led team owns the outcome end-to-end.


I  Engineering


Software engineering & build

Our core practice. Senior-led design and engineering of production software — web, backend, data, integrations. Owned end-to-end through to release.
Example deliverables


Reference architecture & ADRs
Production system delivered iteratively
GitOps pipelines, observability, test stack
Handover documentation aligned to QMS
When to call us 


New plaforms, replatforming, or build-outs that have to shop
 Proof


Case Study Federal-scale collaboration platform →

II  Advisory


Strategic & technical advisory

Senior business and technology judgement from people who have run regulated environments — Tier-1 financial services and public administration. C-level advisory, board-facing opinions and architecture calls, embedded in delivery rather than packaged as a workshop deck.  
Example deliverables


— C-level & board advisory on digital strategy
— Regulated-industry programme & vendor assurance
 Architecture review and technical due diligence
 Fractional CTO / Head of Engineering
When to call us 


Boardroom decisions, regulated transformations, pre-investment reviews, or when something feels off.
 Proof


Case Study Accounting-as-a-Service for regulated SMEs →
III  Operations


Platform & operations

We run what we build. SRE, observability, on-call, change and incident management — under an ISO-aligned QMS, on AWS, Google Cloud, Azure.
Example deliverables


— Cloud landing zone & platform
— Observability, alerting & on-call rota
— Incident, change & release management
— SLAs and operational reporting (99.9% measured)
When to call us 


Going to production, taking over an unmaintained system, or scaling out.
 Proof


Case Study Continuous vulnerability monitoring at scale →
​04 · Troughline


​​​​​​

Governance is not the break. Its the steering.

Delivery governance & audit-readiness — built into all three.


Most regulated programmes fail not at the build, but at the audit. We invert that — the evidence trail is the deliverable, and the working software ships alongside it.


Partner statement · Zürich


Quality Gates Built into every sprint, not bolted on at the end.


Traceability Decision-to-deployment audit trail across every engagement.


Compliance docs QMS-aligned evidence generated from day one — not day 300.


Programme oversight Senior steering and vendor governance on every delivery.

B




​32 · Engagement

Aligned incentives,

transparent meters.

We avoid both extremes — fixed-price scope games and open-ended body-leasing. Most engagements move through three phases. You can exit at the boundary of any of them.

Stage A

Capped-hours discovery

Typical: 2–4 weeks

A fixed, capped budget to understand the problem before quoting the work.


  • Defined scope, defined ceiling — no surprise invoices
  • Senior partner leads from day one
  • Ends with a written opinion you can act on

Stage B

T&M with timesheets

Typical: 3–18 months

Time-and-materials delivery with transparent timesheets and weekly governance.


  • Senior-led, blended Swiss + offshore team
  • Weekly burn report, monthly steering
  • Stop, slow down or scale up at any sprint boundary


Stage C

Retained advisory & operations

Typical: rolling 6–12 months

Ongoing senior judgement and SRE coverage once delivery stabilises — fractional, not full-time.


  • Fixed monthly retainer
  • Named partner + on-call rota
  • Quarterly review against business outcomes



​33 · Engagement

From first call

to delivery.

We avoid both extremes — fixed-price scope games and open-ended body-leasing. Most engagements move through three phases. You can exit at the boundary of any of them.

01

Conversation

Thirty minutes with a partner. We tell you whether we are the right firm.

02

Capped discovery

Two to four weeks to form a defensible opinion of the work.

03

Engagement letter

Scope, governance, team, rates and exit boundaries — all in writing.


04

Delivery

Weekly cadence, monthly steering, QMS-aligned evidence trail.


​34 ·  Engage


​​​​​​

Tell us what you are trying to do.

A thirty-minute conversation with a partner — no pitch deck, no junior intermediaries.


​​Start a conversation →