Not sure yet
Audit
€600–1,800fixed price · 1–3 days
A deep look at an existing system before you decide anything.
- Repo, infrastructure and integrations reviewed
- Written summary with identified risks
- Price deducted if we continue
How we work
Architecture first, code second. No months of analysis with nothing to show.
Short phases with well-defined outputs — an architecture proposal, a working release, a runbook. You always know what you pay for and what you get for it.
48 h call → written proposalEvery Friday a demo
30 days of free fixes after handover
milestoneweekly demooptional
Five phases
What happens — and what you hold at the end of it
These are not sequential gates that close. Phases 1–2 run before a contract, phases 3–5 after signing. On bigger projects they overlap.
Tip: the bars in the chart above open the same phases.
30 min – 3 days
Discovery
We understand the problem before proposing a solution. We ask about business context and verify the technical state ourselves. Goal: we know what must be built and what is risky about the project.
- 30-min free call — quick fit check
- Optional paid audit (1–3 days): repo, infrastructure, integrations
- Written summary with identified risks
You keepRisk summaryAudit report (optional)
What it looks likeWant a quick self-check first? Take the 2-minute audit
risk-summary.mdsample
HIGHERP ↔ e-shop sync runs as a nightly script; failures go unnoticed until month-end.
HIGHNo alerting on failed background jobs.
MEDOne person knows how to deploy to production.
48 hours – 2 weeks
Architecture & plan
We design the solution on paper before touching the keyboard: diagrams, technology choices, phasing, budget. You know what we will build and why — without committing to us.
- Architecture document (40% diagrams, 60% decisions)
- ADRs (Architecture Decision Records) for key choices
- Effort estimate by phase and critical assumptions
- Team structure proposal (if needed)
You keepArchitecture documentADRsEstimate & plan
What it looks like
Call → proposal48 h
- T+0Call
- T+4hNotes
- T+24hSketch
- T+40hEstimate
- T+48hProposal
adr/007-message-bus.mdaccepted
Use a message bus instead of direct calls between systemsDecision Azure Service Bus with retries and a dead-letter queue.Trade-off + failures are visible and recoverable · − one more component to run
2 weeks – 6 months
Build
Weekly sprints, a demo every Friday. CI/CD runs from day one, so every commit goes through builds and tests. If something fails, we know before you do.
- Weekly demo + changelog for stakeholders
- Code with tests, code reviews, lint gates
- Staging environment from week two
- Incremental production deploys (no "big bang")
You keepCode in your repoCI/CD pipelinesObservability
What it looks like
Friday demo · week 6changelog
SHIPPEDOnline booking with deposit payment · invoice export to accounting
MOVEDInsurance claims batch — validation rules 70 %
BLOCKEDWaiting for payment-gateway production keys (client side)
pipeline · main #4824 m 12 s
✓ build✓ tests 412✓ staging production · approve
1–2 weeks
Handover
We do not dump documentation and vanish. We walk your team through the system, write runbooks for common ops situations and accompany them through the first on-call. Goal: after 2 weeks without us, you can run and fix the system.
- Runbooks for incidents, deploys, rollback, scaling
- Architecture walkthrough with recording
- Shadow on-call — we accompany you through the first incident
- Code ownership matrix (who decides what)
You keepRunbooksRecordingsOwnership matrix
What it looks like
runbooks/rollback.mdv3 · updated last week
## Roll back a release 1. Pipeline › Releases › pick the last green one 2. Swap slots: staging ⇄ production 3. Check /health returns 200 within 2 min 4. Post in #ops: what, when, why # Owner: your team · Backup: CodeDock
- Walkthrough recorded
- Shadow on-call done
- Ownership matrix signed
Optional, ongoing
Support
After handover we stay available — either a retainer for continued development, or on-call backup for critical incidents. Or nothing, if everything runs. We do not push monthly fees.
- 30 days of free fixes for anything we delivered
- Optional retainer (monthly hour cap)
- On-call backup for P1 incidents (SLA contract)
You keep30-day warranty
What it looks like
30 days of free fixes. If something we delivered fails after handover, we fix it at no cost.
RetainerContinued development with a monthly hour cap
On-call backupFor P1 incidents, under an SLA contract
NothingIf it runs, it runs. Email us when something comes up.
In practice · ClinicDent
A complete dental-clinic system — web app, booking portal and iPhone app on one API — built this way and running in production.
Read the case study- months of development
- 3.5
- commits
- 250
- modules
- 18
- integrations
- 9
How we charge
No surprises on the invoice
We always tell you up front what things roughly cost. The model follows the work — not the other way round.
30 days of free fixes after handover
Most projectsMost common
Build
Time & materialsmonthly invoicing · or fixed for clear scope
You pay for the work done, and every Friday you see what that work produced.
- Estimate per phase before we start
- Weekly demo + changelog
- Fixed budget for well-defined work (migration, integration)
After handover
Retainer
Monthly hour capoptional · we do not push it
Continued development or a safety net — only if you want it.
- Continued development with a capped budget
- On-call backup for P1 incidents (SLA)
- Or ad-hoc T&M when something comes up
How we communicate
Async where it is enough. Sync where it makes sense. We will not flood you with Slack.
Weekly demo
30 minutes every Friday. What was delivered, what moved, what is blocked. Recorded if you cannot attend.
Dedicated Slack/Teams channel
Shared space with your team. Quick questions, demo videos, PR preview links.
Async decisions via ADRs
Database, cloud provider, auth strategy — written down, not lost in a forgotten Slack message.
PR reviews as dialogue
If you have an internal team, we review their code and they review ours.
Tooling we use
We do not build a custom toolchain on every project. Standards that your people know work just fine — per your preference.
- Code
- GitHubAzure DevOps
- Cloud
- AzureCloudflare
- Tickets
- LinearJiraGitHub Issues
- Chat
- SlackTeams
- Diagrams
- MermaidExcalidraw
- Monitoring
- App InsightsGrafanaDatadog
Client portal
See what we are working on. Online, any time.
Every custom development client gets access to the CodeDock client portal. No waiting for a monthly report — delivered work, logged time and the status of your requests are available as they happen.
Log in to the client portalLogged time, day by day
Every work entry with date, from–to time, author, task and note. Monthly timesheet per project, export to Excel.
Estimates for your approval
Submit a request right in the portal, with a deadline and attachments if needed. You get a quote in both hours and money, with a delivery date — approve it or send it back for re-estimation.
From request to sign-off
Every request goes through estimate, approval, delivery and acceptance. You see who is working on it, how many of the estimated hours are used and what is waiting for you.
Comments and acceptance in one place
Questions, comments and attachments on every request. Accept finished work, or send it back for rework with a comment.
Screenshots use fictional demo data.
Frequently asked
Something missing? Write to info@codedock.com
How much does discovery cost?
The first 30-min call is free. A paid audit (1–3 days, €600–1,800) is optional for deeper assessment of an existing system. Its cost is deducted if we continue the engagement.
Do you work fixed budget or T&M?
Most commonly time & materials with monthly invoicing. Fixed budget makes sense for clearly scoped work (audit, specific migration, integration). We always tell you up front what things roughly cost — no nasty surprises.
How fast can you start?
Usually within 1–2 weeks from the first call. Architecture proposal within 48 hours. Critical incidents (P1) we can tackle within 24 hours of contact.
What if something breaks after handover?
For 30 days after handover we fix bugs for free — if something we delivered fails. Beyond 30 days, either a retainer (monthly hour cap) or ad-hoc T&M.
Do you work alone, or do you have a team?
The project is always led by a senior architect. For the build phase we bring specialists (frontend, DevOps, data) based on what the project needs. You never get a team of juniors without senior oversight.
Start with 30 minutes. Proposal in 48 hours.
No sales pressure. No presentations. You describe the problem, you get direct technical feedback.Pick a timeDirectly with a senior architect. 30 minutes, free, no commitment.Not ready to talk? Take the 2-minute audit →