Question 1

Who actually writes the code?

Accepted Answer

Idin personally owns architecture and the critical code paths — no subcontracting to a junior team. Trusted collaborators may handle scoped, well-defined work on larger engagements, always under founder review.

Question 2

How small is 'boutique'?

Accepted Answer

Boutique on purpose — Idin plus occasional trusted collaborators on specific engagements. We do not pretend to be a 50-person team, and we will not bid as one.

Question 3

Can you scale up if the project grows?

Accepted Answer

Within the boutique model, yes — we add capacity from a known network and stay accountable for delivery. For larger scope we will recommend or co-deliver with a partner agency rather than hire-and-pray.

Question 4

Do you sign NDAs?

Accepted Answer

Yes. A standard mutual NDA is available before the discovery call — just ask and we will send it over.

Question 5

Why don't I see fixed prices?

Accepted Answer

Engagement pricing depends on scope, risk, and timeline — three things that need a 20-minute conversation to scope honestly. A discovery call gives a working range within 24 hours.

Question 6

What are typical price bands?

Accepted Answer

Fixed-Scope MVP starts at $5K. Embedded Retainer runs $3K–$10K per month. Technical Advisory sits between $1K and $5K. Final scope dictates where in the band a project lands.

Question 7

Do you accept Indonesian rupiah or USD only?

Accepted Answer

Both. Local IDR invoicing is available for Indonesian clients; USD goes via Upwork or direct wire for international clients.

Question 8

Are there setup fees?

Accepted Answer

No setup fees. The first invoice covers actual work — discovery, spec, or the opening sprint depending on the engagement model.

Question 9

What's your default stack?

Accepted Answer

Next.js 15 with React 19 on the frontend; Go (Chi) or Python (FastAPI / Django) on the backend; PostgreSQL plus Redis; Docker for everything. We adapt to your stack when it actually matters.

Question 10

Do you only work with AI?

Accepted Answer

No. AI integration is one of five services — most engagements are full-stack web and backend work where AI is an option, not the headline.

Question 11

Can you work with our legacy codebase?

Accepted Answer

Yes. System modernization is a dedicated service — we migrate without losing what works, using strangler-fig, feature flags, and behavioural parity tests to keep production stable.

Question 12

Who owns the source code?

Accepted Answer

You do. Full ownership is transferred via repo access from day one — no vendor lock-in, no hidden license, no escrow gimmick.

Question 13

What about the architecture decisions?

Accepted Answer

Documented inside the repo. Architecture is a deliverable, not a black box — diagrams, ADRs, and runbooks live next to the code.

Question 14

What if we want to switch agencies later?

Accepted Answer

Handoff is part of every engagement. Docs, runbooks, and a clean Git history mean another team can pick up the codebase without reverse-engineering our decisions.

Question 15

What happens after launch?

Accepted Answer

Every engagement includes a fixed post-launch support window for bugfixes and small refinements. An optional retainer transition is available when ongoing work makes sense.

Question 16

Are you available across time zones?

Accepted Answer

We work on WIB (UTC+7) and are responsive Monday to Friday during Indonesian business hours, with emergency response Saturday morning. Most engagements run async-first, so overlap matters less than predictable communication.

Common questions

Engagement

Pricing

Tech Stack

Ownership

Support

Question not answered?