Calda

Introduction

How Calda runs your project end-to-end.


Welcome to your Calda Client Handbook. This space documents everything you need to set up your tools, follow your project, and ship your app with us.

You don't need to be technical to follow along. This handbook explains how we build your product and what we'll need from you, in plain language.

What this handbook covers

  • The way we work together — communication channels, meetings, and how to report issues.
  • The integrations you'll set up — accounts and services we need access to (App Store, Play Console, and more).
  • Publishing your app — the listing details and assets we need from you to submit to the App Store and Google Play.

If you ever feel lost, the sidebar mirrors the order we usually move through during a project.

Your project, stage by stage

Every Calda engagement moves through the same workflow, so you always know what's happening and what's next.

  1. Handoff & preparation. Once the agreement is signed, our sales team hands your project to a dedicated Team Lead, who becomes your main point of contact. They consolidate everything known about the project and prepare for kick-off.
  2. Kick-off call. We introduce the team, agree on tools, communication, and weekly meeting cadence, explain how hours are tracked, and confirm scope, milestones, and immediate next steps.
  3. Design — UX. Designers map user flows, wireframes, and how core features work. You review this and we iterate until it's approved.
  4. Design — UI. We then build the visual design system and final screens in Figma. You review again and we iterate until sign-off. (Backend and database groundwork often starts in parallel here.)
  5. Development. Approved designs are broken into tickets and built in sprints — frontend, backend, integrations, and infrastructure — with weekly updates so you can follow progress.
  6. Testing & QA. We test for bugs, performance, and design accuracy, so the product is solid before it reaches your users.
  7. Deployment & launch. Web apps go live to production; mobile apps are submitted to the App Store and Google Play, including their review process.
  8. Post-launch & support. We fix any launch issues and stabilize the product, then wrap up the project. Many clients continue with us on ongoing support, maintenance, or new features.

If the scope shifts

Sometimes new ideas or requirements come up along the way. If that changes the agreed scope, your Team Lead will flag it early and we'll align on any adjustments together before moving ahead.

How we work

  • Weekly sync. One live call per week to review progress and unblock anything that needs a real conversation.
  • Clear sign-offs. You review and approve design and key decisions before we build on top of them.
  • Async by default. Most decisions happen in writing so they stay searchable.
  • Build-once handoffs. Whatever we build is yours; we document credentials, repos, and deploy flows so you're never locked in.

On this page