Skip to content

How we work

A transparent way to build serious software

Every Navelo Software engagement follows the same principles: a written scope before work starts, working software every week, senior people doing the work, security and quality built in, and full ownership for you. Here is exactly what that looks like.

Delivery process

From first call to production.

Six stages, each with a clear output you can review. Smaller projects move through them in weeks; larger platforms repeat the build stage in releases.

  1. 1

    Discovery

    Workshops with your team to map users, goals, risks and constraints. You receive a written scope, a proposed architecture, a delivery plan and a fixed quote or monthly estimate.

  2. 2

    Design

    User flows, wireframes and a clickable prototype of the key journeys, tested with real users where possible, plus a design system the build follows.

  3. 3

    Build in weekly sprints

    Working software every week: a live demo, a written update and a build you can try on staging, web or your phone.

  4. 4

    Quality assurance

    Automated tests, code review on every change, accessibility and performance checks, and testing on real devices and browsers before release.

  5. 5

    Launch

    Production infrastructure, monitoring, analytics, store submission and a release plan, so launch day is uneventful.

  6. 6

    Care and growth

    Monitoring, updates, fixes and new features after launch, or a documented handover to your own team.

Engagement models

Four ways to work together.

Choose by how well the scope is known and how long you need us. You can switch models as the product matures.

  • Fixed-scope project

    A clearly defined product or feature, delivered against a written scope, timeline and milestones.

    Best for
    MVPs, launches, rebuilds and well-defined features.
    Pricing
    Fixed quote after discovery, paid by milestone.
  • Dedicated product team

    Designers and engineers working as your product team, with a shared roadmap, sprint planning and weekly demos.

    Best for
    Growing products with changing priorities.
    Pricing
    Monthly, based on team size. Scale up or down with notice.
  • Care & growth retainer

    Monitoring, updates, security patches, fixes and steady improvements after launch.

    Best for
    Live products that need to stay healthy and keep improving.
    Pricing
    Monthly allocation agreed in advance.
  • Consulting sprint

    A short, focused engagement with a written outcome: architecture review, AI strategy, due diligence or project rescue.

    Best for
    Big decisions and second opinions.
    Pricing
    Fixed fee for a defined set of questions.

Communication

What you can expect every week.

  • A live demo every week

    Scheduled around your time zone. You see real progress, not slides.

  • Written updates

    What shipped, what is next, decisions needed and risks, in plain language.

  • Direct access

    A shared channel with the designers and engineers doing the work, not a layer of account managers.

  • Shared boards and repositories

    You can see the backlog, every change and every release at any time.

Engineering standards

Quality is a process, not a promise.

The defaults on every project, whatever the size, so the product stays maintainable long after launch.

  • Code review on every change before it merges
  • Automated tests for business-critical logic and user journeys
  • Continuous integration and repeatable, one-click deployments
  • Performance budgets and Core Web Vitals checks for web products
  • Accessibility to WCAG 2.2 AA as the default target
  • Typed code end to end where the stack allows it
  • Error tracking, logging and uptime monitoring from day one
  • Documentation, architecture notes and runbooks kept with the code

Security & data protection

Your data and systems, handled carefully.

Practical safeguards we apply on every engagement. For regulated products we work alongside your security and compliance advisers.

  • Least-privilege access

    Team members get only the access a task needs, through your accounts, and access is removed when the work ends.

  • Secrets kept out of code

    Keys and credentials live in managed secret stores, never in repositories, chat or email.

  • Encryption by default

    Data encrypted in transit and at rest, with sensitive fields minimised or kept on the device where possible.

  • Dependency and vulnerability checks

    Automated scanning of third-party packages, with security updates applied promptly.

  • Backups and recovery

    Automated backups with tested restores, so a mistake or outage is recoverable.

  • Privacy-aware design

    Collect only what the product needs, with consent and data-subject rights designed in for GDPR and similar laws.

Responsible AI

How we build AI you can trust in production.

Agents, chatbots and automations are only useful if they are reliable, explainable and affordable. These rules apply to every AI system we ship.

AI agent development
  1. 01

    Evaluated before launch

    Every AI feature is tested against a set of your real cases for accuracy, cost and speed, and re-tested on every change.

  2. 02

    Humans approve what matters

    Actions that move money, data or customer communication go through approval steps until the evidence supports more autonomy.

  3. 03

    Everything is logged

    Prompts, retrieved sources, tool calls and outcomes are recorded so any answer or action can be traced.

  4. 04

    Your data, your choice of model

    We use provider settings that keep your data out of model training, and offer private, self-hosted models when data must stay in-house.

  5. 05

    Cost limits in code

    Budgets, rate limits and model routing keep usage costs predictable as volume grows.

Technology

Proven tools, chosen per project.

We pick mainstream, well-supported technology your future team can hire for. These are the tools we use most often; the right stack depends on your product.

Web front-end
ReactTypeScriptNext.jsTanStack StartTailwind CSSAstro
Mobile
Swift & SwiftUIKotlin & Jetpack ComposeReact NativeExpoFlutter
Backend & APIs
Node.jsPythonFastAPIGoRESTGraphQLWebSockets
Data
PostgreSQLRedispgvectorSupabaseFirebaseBigQuery
AI & LLMs
OpenAIAnthropicGoogle GeminiOpen-weight modelsvLLM & OllamaModel Context Protocoln8n
Cloud & DevOps
AWSGoogle CloudAzureVercelCloudflareDockerKubernetesTerraformGitHub Actions
Commerce & payments
StripeRazorpayPayPalShopifyRevenueCat
Quality & observability
PlaywrightVitestSentryOpenTelemetryGrafanaLighthouse
Design & analytics
FigmaDesign systemsPostHogGoogle Analytics 4Plausible

Ownership & handover

Everything we build is yours.

Source code lives in repositories in your organisation. App store, cloud, domain and analytics accounts are registered to you. At handover you receive architecture notes, setup guides and runbooks, so any competent team can take over.

  • 100% of code, designs and IP assigned to you
  • Repositories and accounts in your name
  • Documentation and runbooks included
  • Ongoing care available, never required

FAQ

Working with us.

How does a project start?

With a short call about the problem you want to solve. If it's a fit, we run a discovery phase and send a written scope with a timeline and a fixed quote or monthly estimate. Nothing is billed before you approve it. Start here.

Fixed price or time and materials?

Both are available. Fixed-scope projects suit work that can be clearly defined, such as an MVP or a rebuild. A dedicated team billed monthly suits evolving products where priorities change week to week.

Who owns the code and intellectual property?

You do. Code, designs, documentation, data and accounts are created in your name or transferred to you, and repositories live in your organisation.

How do you work across time zones?

Most communication is written and asynchronous, with a weekly live demo and calls scheduled in overlapping hours. Our team is based in India (IST) and works with clients worldwide.

Can you work with our existing team or codebase?

Yes. We regularly extend existing products: we start with a short code and infrastructure review, agree conventions with your team, and work in your repositories and processes.

What happens after launch?

You choose: an ongoing care and growth retainer, ad-hoc support, or a documented handover to your own developers.

Work with us

Have a project in mind?

Tell us what you want to build. You'll hear from a person within one working day, and the first conversation is free and without obligation.