How we work
A clear process from idea to support.
Every SOHOON engagement follows a five-phase process: Discover, Design, Build, Launch and Support. You know what happens next, what you will see and what we need from you — at every stage.
Discover
Understand before we plan
We start every engagement by listening. We hold structured discovery sessions to understand your goals, your users, your constraints and your definition of success. No assumptions — just questions, context and a shared understanding of what we are building and why.
Deliverables
- Project brief and scope document
- Functional requirements list
- Clear, fixed quote or retainer structure
- Milestone and timeline plan
- Identified risks and open questions
Your role
Share your goals, existing materials, competitor examples and any technical constraints. Attend a 60–90 minute discovery call.
Typical cadence
3–5 business days for most projects
Design
Validate the solution before building it
Once we agree on scope, we design before we build. This phase produces wireframes, prototypes and visual designs that you can review, click through and refine — before engineering time is spent. It is the phase that prevents expensive surprises.
Deliverables
- User flows and information architecture
- Low-fidelity wireframes for all key screens
- High-fidelity visual designs (desktop and mobile)
- Interactive prototype for user testing
- Design system and component library
Your role
Review designs in our shared Figma file. Give feedback in rounds — we manage the version history so nothing is lost.
Typical cadence
1–3 weeks depending on product complexity
Build
Develop in sprints with full visibility
Development happens in focused, time-boxed sprints — usually one to two weeks each. At the end of every sprint you see a live demo. You can test it, give feedback and influence the next sprint's priorities. No black box, no big reveal at the end.
Deliverables
- Working software at the end of each sprint
- Automated tests for critical paths
- Staging environment for client review
- Sprint demo and progress report
- Documentation for any integrations or APIs
Your role
Attend sprint demos (30–45 minutes) and give feedback within 2 business days so we can incorporate it immediately.
Typical cadence
1–2 week sprint cycles throughout the build phase
Launch
Ship with confidence, not hope
Before we go live, we run a thorough pre-launch checklist — performance, security, browser testing, SEO foundations, analytics and monitoring. We deploy, verify everything is working and hand over access with full documentation and, where needed, a training session.
Deliverables
- Pre-launch quality assurance report
- Production deployment
- Analytics and monitoring configured
- Full handover documentation
- Training session (where applicable)
Your role
Sign off on the staging environment and provide any final content. Be available for the launch window in case of questions.
Typical cadence
1–3 days for the launch process itself
Support
Stay close after go-live
We do not disappear after launch. Whether you need ongoing maintenance, feature development, performance tuning or fast help when something breaks — we are here. Most clients stay on a monthly support retainer; others call on us as needed.
Deliverables
- Ongoing maintenance and security updates
- Bug fixes with fast response times
- Performance monitoring and optimization
- Feature additions and improvements
- Monthly summary reports (on retainer)
Your role
Log requests via email or our shared task board. Priority levels are agreed upfront so you always know the expected response time.
Typical cadence
Ongoing — flexible monthly retainer or on-demand
Transparency
You are never out of the loop
Unclear communication is the number one cause of failed projects. We have built habits and tools into every engagement to keep you fully informed without overwhelming you.
Weekly status updates
Every week you receive a written update covering what was completed, what is next and any decisions we need from you — no chasing required.
Shared project board
Tasks, milestones and acceptance criteria are visible to you at all times. Nothing is hidden in our internal systems.
Direct access to your team
You have a named project lead and can reach the engineers working on your project — not just an account manager who relays messages.
Decisions in writing
Any scope change, delay or design decision gets confirmed in writing so there are no misremembered conversations later.
Start the process
Let’s kick off your discovery
The first step is a conversation. Tell us what you are working on and we will walk you through exactly how we would approach it.