Process
Every lane uses the same execution rhythm so the scope stays visible, the pricing stays understandable, and nobody wonders what happens next.
The point is not to make the process feel fancy. The point is to make it hard for work to disappear into silence.
/ 01 - Intake
You submit the lane-specific intake — goals, constraints, examples, and urgency. Komlan reviews it personally and comes back within 24 hours with questions or a scope draft. No sales call required to get started.
/ 02 - Scope
Komlan sends a written scope: pages or features, fixed price range, timeline, and assumptions. Nothing starts until you've reviewed and approved it in writing — no verbal agreements.
/ 03 - Build
Work runs through your private workspace. You see every milestone as it ships, submit feedback in one place, and approve before anything goes live. Komlan is the only person building — no subcontractors, no handoffs.
/ 04 - Launch
QA, domain setup, analytics, and a documented handoff of everything you need to maintain the work. You own all the files. If you want ongoing support, a care plan is available — but there's no pressure or lock-in.
Who does the work
Every project at CrecyStudio runs through Komlan Kouhiko — not a project manager, not a junior developer. When you submit an intake, Komlan reviews it. When you have a question, Komlan answers it. When the work ships, Komlan built it.
By lane
What changes
Most projects land in the 2-4 week range depending on page count, copy readiness, and revision speed.
What changes
Store builds, fixes, and ops retainers use the same rhythm, but the scope shifts based on storefront complexity and operational load.
What changes
Automation projects always begin with diagnosis first so we solve the bottleneck instead of automating a broken process.