LET'S TALK.
Start by telling us what's in your way right now.
Whether it's a project, a partnership or a career with us, start by telling us where things stand.
It's fine if you're still sorting out an idea or checking whether it's technically feasible.
We review every message, and a member of our team will get back to you within 2 business days.
On this page, we walk through how we work for each type of request and how product development unfolds, with the contact form at the end.
The first step depends on what you're asking for.
- PRODUCT
Product & system development
New businesses, platforms, business systems, AI integration and more
- 01Discovery
- 02Estimate
- 03Contract
- 04Development kickoff
- 05Operation & improvement
- 06Operations handover
- CREATIVE / PARTNER
Web, landing page & video production, partnerships
Websites, landing pages, video ads, business partnerships and more
- 01Meeting
- 02Estimate
- 03Contract
- 04Production kickoff
- SPOT
One-off requests
Development support, SEO support, technical consultations and more
- 01Consultation
- 02Estimate per request
- 03Kickoff
Here's how product development unfolds.
This walkthrough is based on a real project: we launched a B2B operations platform and developed it through its next version.
On cost, we first hear what you need. We give you a rough estimate after the discovery meeting, then a formal quote once the requirements are defined.
- PHASE 01Launch (through MVP release)About 2 months
We start by locking down the screens and workflows in mockups, then move into development. Our in-house designers can also handle the screen design.
Deliverables
- Mockups
- Screen and workflow design
- MVP (minimum viable product)
- PHASE 02Rollout and the switch from current operationsAbout 1.5 months
We put the MVP to work in real operations, handle the switch from your existing workflows to the new system, and run rollout tests.
Deliverables
- Rollout test results
- Transition procedure
- PHASE 03Live operation, and development driven by user responseAbout 3 months
Once the product is live, we build for customer acquisition and adjust the specs to how users respond.
Deliverables
- Usage reports
- Iteratively improved versions
- PHASE 04Next-version developmentAbout 3.5 months
We keep developing the next version month by month, including the admin features operators use.
Deliverables
- A new version with admin features for operators and more
- PHASE 05Operations handoverAt contract end
We hand the system and the technology over to your team. After the contract ends, the only costs are actual expenses such as server operation.
Deliverables
- Handover of the system and technology
WHAT WE DO
What we take on
- Requirements definition, and screen and workflow design
- UI/UX design (by our in-house designers)
- Development, testing and release
- Progress shared through tickets, and reviews in regular meetings
WHAT SETS THE PLAN
What sets the timeline and team
- The number of features and screens
- How many external services and existing systems it connects to
- Whether it has AI features, and the accuracy they need
- The complexity of permissions and approval flows
- The level of security and availability required
SPOT
One-off requests
One-off requests have no regular meetings. We focus on the work for the period it needs.
We agree on the scope together and quote each request separately. We manage the work in tickets and report on progress and results.
- Development support
- We work alongside your team on feature development and bug fixes.
- SEO support
- We cover everything from search research to improvement proposals and implementation on your site.
- Technical consulting
- We support design reviews and technology choices, drawing on our hands-on development experience.
At each stage, we pause and check in together.
Building it isn't the finish line. Before and after launch, we check progress against the same questions.
CHECK 01At the first discovery meeting
- Are we aligned on the business challenge and the direction of what we're building?
- Can we picture how it will lead to revenue after launch?
CHECK 02When we propose screens and workflows
- Are you convinced by the screens and workflows?
- Are you comfortable with the timeline, cost and approach?
CHECK 03At MVP release
- Did we release it in a state people can actually use?
- Have we agreed on which numbers to watch after launch, and how to read them?
CHECK 04Monthly development meetings
- Are we deciding the next move together, based on the numbers?
- Is development progress visible in the tickets?
CHECK 05At operations handover
- Can your team keep it running on its own?
- Have the system and technology been handed over?