A written Blueprint, then a fixed-price build.
A network studio for funded seed and Series A founders without a CTO.
You need to ship v1, the board wants a number, and every agency quote is a guess. The Blueprint replaces the guess with a written, fixed price.
One accountable principal in Cluj-Napoca brings in senior specialists per engagement — iOS, backend, web, and design — matched to your scope. Scope, price, and timeline are locked in writing, and the €15,000 credits back in full when you commit.
Two to three weeks of paid work. A written technical architecture, scope, role plan, and a fixed price for the Build. Credits one-for-one against the Build if you commit within thirty days.
iOS, backend, and web — components, boundaries, and the runtime decisions behind them.
Schema, third-party APIs, auth, payments, and storage — mapped before the Build starts.
The disciplines your Build needs, named in the Blueprint — with the principal accountable for staffing each one.
From kickoff through launch handoff. Milestones tied to outcomes, not stand-ups.
What could slip, why it would slip, and the mitigation written against each line.
One number. Locked at signature. No surprise re-scoping mid-engagement.
If you don’t commit to the Build, you keep the document. The Blueprint is the cheapest test of whether Carpathcode is the right shape for the problem — before either party signs anything beyond it.
Three honest answers: right fit, alt shape, wrong shape. The Blueprint shows which one applies before any contract is signed.
A clear product to ship, a board that wants budget certainty, and a launch window the Blueprint can plan against. Comfortable with one accountable principal owning the engagement, with collaborators plugged in as scope demands.
A funded company with engineers in place that needs senior iOS, design, or web help for a specific launch window. That is the single-discipline drop, not the full Build — smaller scope, shorter clock, fixed price.
This studio does not run enterprise transformation programs and does not take time-and-materials engagements without fixed scope. The Blueprint will say so out loud if the brief lands there.
You see the price before each phase and can stop after any of them, keeping everything built so far. Blueprint qualifies the work, the Build ships v1, Embedded runs after launch.
What happens in each phase, what ends it, what handoff looks like. The calendar is locked in the Blueprint, not on this page.
Carpathcode is a network studio, not an agency. One accountable principal owns every engagement; senior collaborators plug in where the work demands them.
A single technical principal in Cluj-Napoca owns the engagement, plus collaborators in iOS, backend, web, and design who plug in as the scope demands. The principal is on every call, in every pull request, and accountable for what ships.
Collaborators are senior operators paid as contractors, brought in only where the work requires their craft. There is no junior bench and no project-manager layer. The Blueprint phase decides the role mix and names the people before any of them sign an engagement — and if the right collaborator for a brief isn’t available, the Blueprint says so in writing.
The Build phase invoices once, at the fixed price agreed in the Blueprint. The launch handoff goes to your full-time CTO, not back to the studio — with the repository, cloud accounts, App Store listing, and a written hiring plan for the team you grow next.
The model drafts. The toolchain checks. The engineer decides. Three layers, named tools, no marketing slop.
An LLM runs in the editor alongside Xcode. It drafts SwiftUI views and view models, Codable types from JSON samples, Core Data and SwiftData migrations, XCTest and Swift Testing cases against acceptance criteria, mock API clients, and the first pass of App Store copy.
Every commit is built and tested on Xcode Cloud. SwiftLint and SwiftFormat pass before merge. Unit and snapshot tests catch regressions across the iOS target. Xcode Cloud handles signing, archive, and TestFlight uploads natively — no third-party build glue. A real toolchain tests every build before it ships.
Architecture and module boundaries, data flow and Swift concurrency, what makes the cut for launch, store-submission and launch strategy, every line of production code reviewed, and the hiring plan handed to your future CTO — all decided by the principal and named collaborators, never by the model alone.
Every engagement shape, what it costs, how it bills, and what transfers when. No surprises after the call.
What funded founders ask before signing the Blueprint. Plain answers.