Paeth Solutions
Folge-Engagement·Build Sprints folgen nachSprint Zero
2–12 Wochen · T&M oder Festpreis

Build Sprints — from plan to production-ready software.

Two to twelve weeks of focused engineering. Weekly demo cadence. Shared backlog. Clear ownership. Result: software you can ship to your customers.

Plan a sprintModi vergleichen

Abrechnungs-Modi

Modes:

Variante 1

Time & Material

Hourly rate on request

  • Weekly reports, transparent burn
  • Recommended for: exploratory scope, new feature lines
Klarer Scope

Fixed Price

By scope

  • Clear acceptance criteria, change-request process
  • Recommended for: clearly defined deliverables
  • 15% risk buffer included

Wochenrhythmus

Sprint anatomy.

Concrete weekly cadence, the same every week. No improvising with status calls.

  1. Monday

    Sprint planning, 90 minutes. Joint prioritization in the Linear/Jira backlog.

  2. Tuesday to Thursday

    Build. Asynchronous updates in the Slack channel, no daily call.

  3. Friday

    Demo (30 to 45 minutes) plus retro. Written weekly status with burn chart by Friday evening.

Sprint-Inhalt

What's included:

Weekly demo + retro

Shared Slack/Teams channel

Linear/Jira backlog

CI/CD from day 1

Documentation as deliverable

Handover sprint at the end

Typische Outcomes

Example outcomes:

SaaS MVP from 0 to betaStripe subscriptions + customer portalStrapi headless CMS migrationNestJS backend refactorAI feature integration into existing app

Entscheidungshilfe

Fixed price or Time & Material.

KriteriumFestpreisTime & Material
Scope clarityhighlow to medium
Risk buffer15 % in pricewith the customer
Change requestsformal processflexible
Best forclearly scoped modulesexploratory builds

Klare Abgrenzung

What we don't build.

Native mobile apps (iOS/Android Native) as the main product.
Blockchain or crypto platforms.
WordPress or Shopware customizing.
Embedded or hardware-near software.
Game development.

Übergabe

Handover and code ownership.

Code belongs to the customer from the first commit.
Git repo lives in the customer account (GitHub or GitLab).
Handover sprint with documentation, runbook, onboarding session.
30 days bug warranty after going live.

FAQ

FAQ Build Sprints.

How many sprints do you run in parallel at most?

Two. At three, demo discipline and code review depth drop. A third mandate goes into the sub-contractor pool or is postponed.

Can we involve external designers?

Yes. We work well with Figma-first designers. Handover via Figma link with component library, implementation in Tailwind or CSS Modules per spec.

Who is the contact during the sprint?

Directly the engineer who builds. No account manager, no handover chain. In Strategic retainer also in your team's standup.

What happens with sickness or vacation?

Planned vacation: shifted by the vacation duration, agreed in advance. Sickness over 3 days: sub-contractor pool steps in, transparently communicated. Sprint depths are secured jointly with the customer.

Build Sprint planen

Vom Plan zur produktionsreifen Software.

Jeder Build Sprint folgt nach Sprint Zero. Wenn der noch fehlt — buchen Sie zuerst Sprint Zero, dann planen wir den passenden Sprint.

Mit Sprint Zero startenPlan a sprint

One-Pager zum Mitnehmen

MVP in X WochenPDF · Festpreis-BuildLegacy-Rescue / Architektur-AuditPDF · Festpreis-Audit