Services — Tessvik

$ cd ~/tessvik/services

Strategy, design, engineering and operations from one team. Pick a starting point; we'll staff the rest.

5 services · 3 ways to engage

(05) — What we ship

Hover or tab through
↑ ↓ to move

(01)2-week discoveryRoadmap · prototypes · estimatesProduct strategy→

(02)8–14 weeksNext.js · Postgres · StripeWeb platforms→

(03)10–16 weeksSwift · Kotlin · React NativeMobile apps→

(04)4–8 weeksRAG · evals · guardrailsAI features→

(05)OngoingAWS · Terraform · 99.95% SLOCloud & DevOps→

{}Every engagement starts with a two-week discovery sprint and a fixed quote.Book a sprint

(02) — Ways to work with us

Three ways in. One team either way.

01 · Discovery sprint

fixed · 2 weeks

Find the one number the build has to move, then cost it properly.

✓10 user + team interviews
✓Analytics audit
✓Clickable prototype
✓Technical plan
✓Fixed quote for the build

Book a sprint →

02 · Build teamMost chosen

per month · from

A named team of 3–6 that designs, builds and ships with you every two weeks.

✓Product lead + designer
✓2–4 engineers
✓Fortnightly demos
✓Staging from day three
✓Weekly written update

Start a build →

03 · Run & evolve

per month · from

We stay on the pager and keep improving what we shipped.

✓24/7 on-call, 15-min response
✓99.95% SLO in writing
✓Monthly metrics review
✓Security patching
✓2 days of new work / month

Talk about support →

Prices exclude tax. Conversions are indicative; we invoice in CAD or EUR.

(03) — How we work

Six steps. One team the whole way.

03 · BuildWeeks 3–10

Two-week sprints with a demo every other Friday. You get a staging link on day three and can watch every pull request land.

You getWorking software, every sprint

(04) — Stack

Boring on purpose.

TypeScriptNext.jsReact NativeSwiftKotlinGoRustPythonGraphQLtRPCTypeScriptNext.jsReact NativeSwiftKotlinGoRustPythonGraphQLtRPC

PostgresRedisKafkaAWSGCPTerraformKubernetesVercelStripepgvectorGrafanaPostgresRedisKafkaAWSGCPTerraformKubernetesVercelStripepgvectorGrafana

01 · Default to boring

Postgres, Next.js and a managed cloud. Your next hire already knows them.

02 · Write it down

Every project gets a one-page record of its architecture decisions and why.

03 · Change with reason

Real-time, offline or regulated? Each yes changes a default, on purpose.

(05) — Shipped this week

Week 39 · 22–26 Sep
Drag or scroll →

Fernloopv4.12.0

+Saved carts sync across devices
+Apple Pay on web checkout
+Address lookup 3× faster

+1,214 −388Mon · ● Live

Harbrook Health2.8.1

+Waitlist fills cancelled slots
+SMS reminders in 6 languages

+642 −120Mon · ● Live

Quillmate0.19.0

+Assistant cites the help-centre page
+Eval suite: 412 new cases
+Handoff to a human in one tap

+2,031 −904Tue · ● Canary 10%

Northvane7.3.0

+Live fault map for 40k sensors
+Alert noise down 62%

+880 −1,403Wed · ● Live

Ledgerline3.0.0

+Pay-by-link on every invoice
+QuickBooks two-way sync

+3,120 −1,450Wed · ● Live

Tidewell5.4.2

+Offline tickets in Wallet
+Seat maps for the 7:40 ferry

+410 −96Thu · ● Live

Orbitra Labsinfra-212

+Moved 14 services to ARM
+Monthly bill down $31k

+96 −740Fri · ● Live

Mapleformds-1.9

+Dark mode tokens
+12 components to Figma variables

+1,502 −377Fri · ● Review

fernloop v4.12.0   ·   harbrook-health 2.8.1   ·   quillmate 0.19.0   ·   northvane 7.3.0   ·   ledgerline 3.0.0   ·   tidewell 5.4.2   ·   orbitra-labs infra-212   ·   mapleform ds-1.9   ·   fernloop v4.12.0   ·   harbrook-health 2.8.1   ·   quillmate 0.19.0   ·   northvane 7.3.0   ·   ledgerline 3.0.0   ·   tidewell 5.4.2   ·   orbitra-labs infra-212   ·   mapleform ds-1.9   ·   

(06) — Questions

Straight answers.

Something else? Ask a named engineer at hello@tessvik.dev.

Most first releases land between CA$180k and CA$420k: a two-week discovery sprint, then 8–14 weeks of a build team. The sprint ends with a fixed quote, so you know the number before you commit to it.

Usually, yes. Your engineers review our pull requests from week one, and by handover they're writing most of them. We plan the handover from the first sprint.

You do, from the first commit. Everything lives in your GitHub organisation and your cloud accounts. We never hold anything hostage.

Yes. We start with a two-week audit of the codebase, infrastructure and analytics, then propose a plan that keeps the lights on while we improve it.

Discovery sprints usually start within two weeks of signing. Build teams take three to four weeks to assemble, because we staff from people, not a bench.

Vancouver and Porto, so between us we cover 16 hours of the working day. On-call is 24/7 for products we run.

(07) — Start

hello@tessvik.dev

Know what you need?

Book a discovery sprint→

We reply within one working day, with a named engineer.

Three ways in. One team either way.

Six steps. One team the whole way.

Boring on purpose.

Eight releases. Zero rollbacks.

Straight answers.

BOOK IT.