Approach

Find, agree,
build, and run.

Unclear requirements are normal. From discovery through monthly ops, we close scope in writing.

Stages

Five stages

  1. 01Intake · meetingWe hear symptoms via intro or KakaoTalk, then a short meeting to decide if discovery is warranted. No prior requirements doc needed.
  2. 02Discovery · report · PTWe embed in the work, find what digitization and AI can shrink, then present findings and what to do now.
  3. 03Contract · SOWIn-scope, out-of-scope, success criteria, build fee, and monthly ops are locked in writing. We do not build everything we found.
  4. 04BuildOnly agreed scope. LLM integration (e.g. Google Gemini) when useful. Extra requests need a new agreement.
  5. 05Monthly operationsHosting, incidents, and agreed small improvements on a monthly retainer. Build is not the end.

Discovery

Before software: make agreement possible

Discovery is not a delivery milestone. It organizes as-is state, candidates, scope, and estimate, then supports decisions with a presentation. Duration and breadth adjust to size.

  • As-is summary
  • Digitization / AI candidates and priority
  • Draft SOW
  • Build and monthly ops estimate outline
  • Decision via presentation

Commercial structure

Discovery · Build · Monthly ops

Paid discovery

Scope lock. Report and presentation so the pain is clear.

Build

Delivered against the agreed SOW. Changes need a new agreement.

Monthly operations

Agreed ops on a monthly fee. New features are separately quoted.

Exact amounts depend on scope. See cases or contact us on KakaoTalk.

Not sure where to start?

Describe the symptoms. We will see whether discovery fits.

Approach | Estampeur