What is the smallest customisation you take on?

A single component or token revision. We do not take on work under half a day because the discovery overhead does not justify it; for very small changes you are better off on our ad-hoc engineering rate.

Do you work on themes that are not stock Hyvä?

Yes if the deviations are documented or visible from a code review. Heavily customised forks get an upfront review session so we can agree the scope honestly.

Will you change our design tokens?

Only where the brief calls for it. Tokens are the spine of the theme; we change them deliberately and document every change so future engineers know the why.

Can you ship without disrupting our content team?

Yes. Customisations land on a branch and ship to staging first. Your content team reviews on staging; we deploy to production only after sign-off.

How do you handle scope creep?

Pause and rewrite the brief. Most customisations have one or two refinements; we batch them at the next milestone. Larger additions become a separate brief.

Hyvä Development

Hyvä Theme Anpassung

Bereits auf Hyvä? Markenauffrischung, neue Abschnitte oder Vorlagen, ohne die Geschwindigkeit Ihres Shops zu beeinträchtigen. Typisches Projekt: 2 bis 4 Wochen.

Timeline: 1 to 4 weeks
Pricing: Fixed
Scope: Tightly defined
Handover: Documented PRs

Overview

What it is.

Für Shops, die bereits Hyvä nutzen und Unterstützung benötigen: eine Markenauffrischung, eine neue Seitenvorlage, eine benutzerdefinierte Komponente oder eine Verfeinerung der Interaktionen. Kleinere Reichweite als ein vollständiger Theme-Bau, eng definiert, Festpreis, wo immer möglich. Am Ende der Entdeckungsphase teilen wir ein schriftliches Briefing, damit Sie genau wissen, was im Umfang enthalten ist und was nicht, bevor Sie sich verpflichten. Der Quellcode gehört Ihnen.

What you get

Deliverables.

Customisation work as scoped in discovery
Updated Tailwind design tokens where applicable
New or revised Hyvä components
AlpineJS interaction adjustments
Documented PRs on your repository
Storybook updates for any new components
QA sign-off on impacted pages

Honest limits

What it isn't.

Customisations to backend modules are quoted separately
Full theme rebuilds belong in the Hyvä theme development service
We do not work on themes that have departed materially from the Hyvä standard without a code review first

Not sure if it's a fit? Email us. We'll tell you straight.

How it works

From inquiry to handover.

01
1. Discovery
Review the existing theme and confirm the scope of customisation.
02
2. Brief
Written brief with the list of changes, agreed before work starts.
03
3. Build
Customisation work in your repository with daily commits.
04
4. QA + handover
Sign-off on impacted pages. Documentation updated.

Frequently asked

Questions we get from people about to book.

What is the smallest customisation you take on?: A single component or token revision. We do not take on work under half a day because the discovery overhead does not justify it; for very small changes you are better off on our ad-hoc engineering rate.
Do you work on themes that are not stock Hyvä?: Yes if the deviations are documented or visible from a code review. Heavily customised forks get an upfront review session so we can agree the scope honestly.
Will you change our design tokens?: Only where the brief calls for it. Tokens are the spine of the theme; we change them deliberately and document every change so future engineers know the why.
Can you ship without disrupting our content team?: Yes. Customisations land on a branch and ship to staging first. Your content team reviews on staging; we deploy to production only after sign-off.
How do you handle scope creep?: Pause and rewrite the brief. Most customisations have one or two refinements; we batch them at the next milestone. Larger additions become a separate brief.

Ready to start?

Tell us about your project.

A member of our team reads every message. Replies within one business day. No sales call required.

See all services

Hyvä Development

Hyvä Theme Anpassung

Bereits auf Hyvä? Markenauffrischung, neue Abschnitte oder Vorlagen, ohne die Geschwindigkeit Ihres Shops zu beeinträchtigen. Typisches Projekt: 2 bis 4 Wochen.

Timeline: 1 to 4 weeks
Pricing: Fixed
Scope: Tightly defined
Handover: Documented PRs

Overview

What it is.

What you get

Deliverables.

Customisation work as scoped in discovery
Updated Tailwind design tokens where applicable
New or revised Hyvä components
AlpineJS interaction adjustments
Documented PRs on your repository
Storybook updates for any new components
QA sign-off on impacted pages

Honest limits

What it isn't.

Customisations to backend modules are quoted separately
Full theme rebuilds belong in the Hyvä theme development service
We do not work on themes that have departed materially from the Hyvä standard without a code review first

Not sure if it's a fit? Email us. We'll tell you straight.

How it works

From inquiry to handover.

01
1. Discovery
Review the existing theme and confirm the scope of customisation.
02
2. Brief
Written brief with the list of changes, agreed before work starts.
03
3. Build
Customisation work in your repository with daily commits.
04
4. QA + handover
Sign-off on impacted pages. Documentation updated.

Frequently asked

Questions we get from people about to book.

What is the smallest customisation you take on?: A single component or token revision. We do not take on work under half a day because the discovery overhead does not justify it; for very small changes you are better off on our ad-hoc engineering rate.
Do you work on themes that are not stock Hyvä?: Yes if the deviations are documented or visible from a code review. Heavily customised forks get an upfront review session so we can agree the scope honestly.
Will you change our design tokens?: Only where the brief calls for it. Tokens are the spine of the theme; we change them deliberately and document every change so future engineers know the why.
Can you ship without disrupting our content team?: Yes. Customisations land on a branch and ship to staging first. Your content team reviews on staging; we deploy to production only after sign-off.
How do you handle scope creep?: Pause and rewrite the brief. Most customisations have one or two refinements; we batch them at the next milestone. Larger additions become a separate brief.

Ready to start?

Tell us about your project.

A member of our team reads every message. Replies within one business day. No sales call required.

See all services

Hyvä Theme Anpassung

What it is.

Deliverables.

What it isn't.

From inquiry to handover.

1. Discovery

2. Brief

3. Build

4. QA + handover

Questions we get from people about to book.

Tell us about your project.

Hyvä Theme Anpassung

What it is.

Deliverables.

What it isn't.

From inquiry to handover.

1. Discovery

2. Brief

3. Build

4. QA + handover

Questions we get from people about to book.

Tell us about your project.