How We Work

Every Visnoa project follows four stages: scope, design, build and test, then demo and handover. We use AI coding tools to speed up the build, while our engineers own the scope, architecture, code review, testing, deployment and documentation. You see working software early and approve each stage before the next begins.

1. Scope

   A focused discovery call and a written scope: users, core journeys, must-have features, exclusions and acceptance criteria.

   Day 1–2

2. Design

   Key screens and the data model are agreed before heavy build work starts, so feedback is cheap and fast.

   Day 2–4

3. Build & test

   AI-assisted development with human review of every change, plus testing of real workflows, permissions and edge cases.

   Sprint

4. Demo & handover

   A live demo, a revision round, deployment where agreed, documentation and full access to your code and accounts.

   Final days

1. Scope: agree what “done” means

We start with a focused conversation about your users, the problem and the outcome you need. We then write a short scope document covering:

• who the users are and what each type of user needs to do;
• the core user journeys the product must support;
• what is explicitly out of scope for this version;
• integrations, data and accounts we will need;
• acceptance criteria, timeline, price and payment milestones.

Nothing is built until you approve the scope. This single step prevents most of the disappointments that happen in software projects.

2. Design: decide cheaply before building expensively

We sketch the key screens and the data model first. Changing a screen layout at this stage takes minutes; changing it after the backend is built takes days. For prototype projects, this stage produces the clickable flow itself.

3. Build and test: fast, but reviewed

We build in short cycles and share progress, usually through a private preview link. AI tools generate much of the routine code; an engineer reviews every change, runs it and tests it against the scope. Testing focuses on what actually breaks products in the real world:

• complete user journeys, not just individual screens;
• permissions — can each user see only what they should?
• empty states, invalid input and failed network calls;
• behaviour on mobile and on common browsers.

4. Demo and handover: you own everything

We walk you through the finished work live, collect feedback for the agreed revision round, and then hand over:

• the source code in a repository you own;
• deployment on hosting in your name, where deployment is in scope;
• a short technical document: architecture, setup, environment variables and known limitations;
• a recorded walkthrough for your team.

How we use AI — and how we do not

AI-assisted development is the reason we can deliver in days what traditionally took weeks. We are also clear about its limits:

• We use AI to scaffold interfaces, generate boilerplate, draft tests and documentation, and explore alternatives quickly.
• We do not ship code nobody has read, paste your confidential data into tools without your agreement, or describe a prototype as production-ready because it worked in a demo.
• We tell you which AI services your product itself depends on (for example a language model API), what they cost and what happens if they fail.

Communication

You get a single point of contact, a shared channel (email, Slack or WhatsApp — your choice), a written update at least twice a week during active builds, and a preview link so you can see progress yourself. For international clients we agree overlapping working hours at the start.

What we need from you

• One decision-maker who can give feedback within a working day.
• Access to any accounts, brand assets and sample data we need.
• Honest feedback at each demo — “this is not what I meant” is useful, early.

Process FAQs