Questions, answered.

We work in three shapes: a Discovery Sprint (2 weeks, fixed fee, written roadmap), a Dedicated Team (monthly retainer that scales with scope), and Project-Based delivery (fixed scope, fixed price, fixed date). Most clients start with Discovery, move to Project-Based for the MVP, then to a Dedicated Team for scale. The right model follows your brief: unclear scope points to Discovery, ongoing platform work to a Dedicated Team, a locked MVP brief to Project-Based.

Discovery Sprints start within 1 week of signing; Dedicated Teams typically onboard in 2 weeks. The first days of any engagement are reserved for context — domain immersion, stakeholder interviews, and tooling access — so the code that follows lands in the right place.

Yes — embedded delivery is the default. We join your standups, your Slack, and your repositories rather than working in a silo. Knowledge transfer is part of the deliverable, not an afterthought: paired delivery and code review keep your engineers in the loop as the work progresses.

Pricing follows the engagement model: a fixed fee for Discovery Sprints, a monthly retainer for Dedicated Teams, and a fixed price against a locked scope for Project-Based work. Every price includes developer time, project management, and standard tooling. Third-party licenses, infrastructure costs, and travel are billed separately — agreed in writing before any work starts.

It depends on scope, team size, and duration — a 2-week Discovery Sprint sits at a very different price point than a 6-month dedicated team. We don't publish rate cards because ranges without context mislead more than they inform. Book a 15-minute call and we'll give you an honest estimate against your actual brief.

Dedicated Teams absorb scope changes naturally — that's the point of the model. Project-Based engagements use change orders: we discuss the impact transparently, re-baseline the plan together, and nothing shifts until you've agreed in writing. Surprises stay in the discovery phase, not the invoice.

You do. The code lives in your repository from day one — we work in your GitHub or GitLab, not ours — and the intellectual property created during the engagement transfers to you. No license fees, no escrow, no lock-in: your code, your repo, your data, exportable at any time.

We work to GDPR standards for our European clients: data processing agreements, a documented sub-processor list, and data-protection obligations flowed down per GDPR Article 28. As an Indonesian entity we also comply with PP No. 71/2019. Where projects involve sensitive data, we design for it — encryption, retention policies, and deployments that keep data inside infrastructure your contracts cover.

You grant access, you control it, and you can revoke it at any time. Our engineers work through accounts you provision, scoped to least privilege — no shared credentials, no access broader than the work requires. Clean offboarding at the end of an engagement is part of the standard process, not an extra.

Jakarta (WIB, UTC+7) gives European teams roughly 4 hours of synchronous overlap every working day — 08:00 CET is 14:00 WIB. Blockers raised at the end of a European day have answers waiting the next morning, because our team keeps working while Europe sleeps. Business hours are Monday to Friday, 09:00–18:00 WIB, and standups and reviews are planned inside the shared window.

Written-first, in your tools. We join your Slack and your standups, work through pull requests with review gates, and keep decisions in writing so nothing depends on someone remembering a call. Progress shows up as shipped, reviewable increments — not status decks.

Every build includes 30 days of post-launch support — we stay on to fix the things that only show up in production. After that, most clients continue with a Dedicated Team retainer for iteration and maintenance, or take over fully: runbooks, documentation, and team training are part of the deliverable either way. We graduate teams; we don't create dependence.