Skip to main content
Kodlify, go to the home page

How we work

Our sports app development process

Four clear steps take your idea from the first call to a live product. At every stage you know what is happening, what you will receive and what comes next.

The four steps

  1. Step 1

    Discovery and strategy

    We learn how your club or business runs, who will use the software and what success looks like. Together we agree priorities, scope and budget, so nothing is left to guesswork.

    Typical duration: Depends on project size

    What you receive

    • A written summary of goals, users and scope
    • Feature priorities: what is essential now and what can wait
    • A fixed quote or a recommended subscription plan
    • A timeline broken into milestones
  2. Step 2

    Plan and design

    We map the user journeys for members, staff and admins, design the screens around your brand and decide on the technical set-up.

    Typical duration: Depends on project size

    What you receive

    • Screen designs or a clickable prototype
    • A technical plan covering hosting, integrations and data
    • A confirmed milestone plan
  3. Step 3

    Build and iterate

    We build in short cycles and show you working software at every milestone. Your feedback goes straight into the next cycle, so the product improves as it grows.

    Typical duration: Depends on project size

    What you receive

    • Working software at each milestone
    • A private test version you can try at any time
    • Regular progress updates
  4. Step 4

    Launch and support

    We put the software live, handle app store submission if needed, move your existing data and train your team. Then we stay on to fix, update and improve.

    Typical duration: Depends on project size

    What you receive

    • Your live website, app or platform
    • Admin training and handover documents
    • 30 days of post-launch support
    • Options for ongoing maintenance

How we keep you in the loop

You should never have to chase us for an update.
One point of contact
A single person on our side who knows your project and answers your questions.
Regular progress updates
A short written update on what was done, what is next and anything we need from you, at a rhythm we agree at kickoff.
A demo at every milestone
You see and try the real software, not slides about it.
Replies within 24 hours
Questions sent by email or WhatsApp get an answer within 24 hours.

Tools we use to collaborate

We fit around the tools you already use, and suggest simple ones if you don't have a preference.
  • A shared project board, such as Trello, Jira or Linear, so you can see every task
  • Video calls on Google Meet, Zoom or Microsoft Teams
  • Email, WhatsApp or Slack for quick questions
  • A private test link where you can try new features before they go live

Two ways to work with us

The process is the same either way. What changes is how you pay and who looks after the software after launch.

Project-based

We agree the scope and a fixed price after discovery. You pay in milestones as the work is delivered, and the custom software becomes yours once it is paid in full. After launch you can maintain it yourself or move to a monthly plan.

Suits clubs and founders with a clear scope and a one-off budget.

Subscription

You pay a one-time setup fee to get your website, app or platform built and launched, then a monthly fee that covers hosting, security, backups, maintenance, bug fixes and support. Larger new features are scoped and quoted separately.

Suits clubs that want a lower upfront cost and a team looking after the software every month.

Questions about our process

How involved do we need to be?

Most involvement happens during discovery and design, when we need your knowledge of how the club runs. During the build, a short review at each milestone is usually enough.

Can we change priorities during the build?

Yes. Because we work in short cycles, priorities can change between cycles. If a change affects the agreed scope or price, we tell you before doing the work.

What do you need from us to get started?

A short description of what you want to fix or build, who will use it and any deadlines. Logos, existing data and access to current systems can follow later.

Can you take over an app someone else built?

Often, yes. We start with a review of the code and hosting, tell you honestly what we find and recommend whether to improve it or rebuild parts of it.

Ready to start with discovery?

Tell us about your club or idea and we will suggest the right first step.