How it works
How it works: from first conversation to launch.
A KodeVine engagement moves through five stages. The first three happen before any development, so you review the proposed solution, the scope, and the plan before you commit to building.
Five stages, three before any build
You decide at each step
- 1First conversationA description of the situation today
- 2Discovery and scopeAccess to the people who do the work
- 3Proposal reviewFeedback and questions
- Building starts only after you approve the proposal.4Build in reviewable stepsTimely feedback on each increment
- 5Launch and handoverLaunch timing that suits your business
Engagement stages
- 01
First conversation
We learn what you are trying to build or fix, and you learn whether we are a good fit.
We ask about the problem, the people affected, the tools involved, and what a good outcome looks like. You can ask anything about how we work.
If the project is not a fit, or a simpler fix would serve you better, we say so.
Before development
What you provide
- A description of the situation today
- The tools and systems involved
- Any timing that matters
- 02
Discovery and scope
We map the workflow, check integrations, and define what the first release includes and excludes.
We look at how the work happens today, which systems need to connect, and where people must stay in control. For AI work, we assess feasibility before recommending a build.
The output is a written scope: what will be built, what is deliberately left out, the decisions you need to make, and the risks we see.
Before development
What you provide
- Access to the people who do the work
- Sample data or screenshots where useful
- Decisions on priorities
- 03
Proposal review
You review the proposed solution, approach, and plan before any development begins.
The proposal explains the solution in plain language, with workflow diagrams or screen sketches where they help. It covers how cost and timing were estimated and what could change them.
Nothing is built until you are comfortable with what is proposed and why.
Before development
What you provide
- Feedback and questions
- Approval to proceed or requested changes
Development starts here, after you approve the proposal
04Build in reviewable steps
We build in short increments you can see and test, adjusting as we learn.
You see working software regularly, along with status updates. Integrations are tested against real systems in a safe environment before launch.
What you provide
- Timely feedback on each increment
- Test accounts for integrated systems
- 05
Launch and handover
We launch carefully, monitor early use, and hand over documentation and access.
Launch includes a checklist, a rollback plan, and monitoring. Handover includes documentation, admin access, and training for the people who will use and own the system.
Ongoing support and improvements can continue after launch if you want them.
What you provide
- Launch timing that suits your business
- People to receive training
Questions about how it works
Before you get in touch
Is the first conversation a sales pitch?
No. It is a working conversation about your problem. You will leave with a clearer view of your options, whether or not we work together.
When do we see a cost estimate?
Once scope is defined. An estimate before we understand the work would be a guess. The proposal explains how the estimate was built and what could change it.
Can we stop after discovery?
Yes. The written scope from discovery is useful on its own, whether you build with us, with another team, or decide not to build yet.
Who owns what we build?
Ownership of code, data, and accounts is set out in the agreement before development begins. We recommend that hosting and service accounts are opened in your company’s name.
Where to go next
- Industries: see where the services fit and what a first conversation covers for your business.
- Example workflows: step-by-step illustrations, including where a person stays in control.
- What to Prepare Before Hiring a SaaS Development Partner: a scoping checklist.
- About KodeVine: our focus and approach.
Start with a first conversation.
Tell us what you’re trying to build or which part of your workflow keeps getting stuck. We’ll reply with questions and an honest view of the options.