PROCESS — FROM FIRST CALL TO DELIVERY

How I work with clients

Jovanni Jungco, a full-stack and AI engineer, takes every project through seven stages: discovery call, brief and scope, blueprint, build, review, launch, and handover. Each stage ends with something you can see and approve, so you always know what is done and what comes next.

Book a discovery callLAST UPDATED ·

The seven stages

01 · TYPICAL TIME · [30–45 min]

Discovery call

We talk through your idea, who it is for, and what a good result looks like. I ask questions and tell you honestly whether I am the right fit.

What I need from you

  • A rough idea or problem to solve
  • Any existing product, brand or links
  • Your target launch date, if you have one

What you get

  • Straight feedback on scope and feasibility
  • A clear yes or no on whether I can help
  • The next step in writing
02 · TYPICAL TIME · [2–3 days]

Brief and scope

I turn the call into a written brief: goals, features, what is in and out of scope, and an estimate with a timeline.

What I need from you

  • Review and correct the brief
  • Answers to open questions
  • Sign-off on scope and budget

What you get

  • A written project brief
  • [Estimate and payment terms]
  • A prioritized feature list (must-have vs. later)
03 · TYPICAL TIME · [3–5 days]

Blueprint

Before writing production code I plan the architecture, data model, third-party services and key screens, so there are no big surprises later.

What I need from you

  • Feedback on screens and flows
  • Access to any services or accounts I need

What you get

  • Architecture and data-model outline
  • Screen flows or wireframes
  • Milestone plan with demo dates
04 · TYPICAL TIME · [depends on scope]

Build

I build in small increments and ship working features to a staging site, so you can see real progress instead of waiting for a big reveal.

What I need from you

  • Quick feedback on each demo
  • Content, copy and assets when needed

What you get

  • [Weekly] demo or progress update
  • A live staging link you can click through
  • Open decisions raised early, not at the end
05 · TYPICAL TIME · [3–7 days]

Review and testing

We go through the whole product together. I fix bugs, handle agreed revisions, and check performance, accessibility and security basics.

What I need from you

  • One consolidated round of feedback
  • Final approval of the build

What you get

  • Bug fixes and agreed revisions
  • Testing across devices and browsers
  • A short launch checklist
06 · TYPICAL TIME · [1–2 days]

Launch

I deploy to production, connect your domain and services, and watch the first live traffic closely.

What I need from you

  • Domain and hosting access
  • Go-live approval

What you get

  • Production deployment
  • Monitoring and error tracking set up
  • A quick walkthrough of how it runs
07 · TYPICAL TIME · [support window]

Handover and support

You get the code, documentation and access. After launch I fix issues in the agreed support window, and we can keep working together if you want to grow the product.

What I need from you

  • Report any issues you find
  • Decide on next features, if any

What you get

  • Source code and documentation
  • [Post-launch support window]
  • Optional ongoing maintenance or new features

Common questions

How does Jovanni work with clients from first call to delivery?

Jovanni works in seven stages: discovery call, brief and scope, blueprint, build, review and testing, launch, and handover with support. Each stage has a clear output, such as a written brief, an architecture plan, or a staging link, so you always know what is done and what comes next.

How does a project start?

A project starts with a discovery call. Jovanni listens to your idea, asks about users and goals, and says honestly whether the project is a good fit. If it is, a written brief with scope, estimate and timeline follows, and nothing starts until you approve it.

How long does a project take?

The timeline depends on the scope of the project. A small, focused build takes less time than a product with payments, AI features or several integrations. Jovanni gives a timeline in the written brief after the discovery call, and splits the work into milestones with demo dates, so you can see progress and adjust priorities along the way.

How does Jovanni price projects?

[Pricing model: fixed price per milestone, hourly, or monthly retainer.] Jovanni sends a written estimate after the discovery call, and the scope in the brief defines what the price covers. Changes to scope are discussed and agreed before any extra work starts.

Which tech stack does Jovanni use?

Jovanni builds with TypeScript, Next.js and React on the front end, React Native for mobile, and Node.js on the back end. Data lives in PostgreSQL, with pgvector for AI search. Jovanni deploys on AWS and Vercel, and uses the Claude API for AI features. The stack is chosen to fit your project.

Does Jovanni build AI agents and RAG systems?

Yes. Jovanni has built an AI customer service agent, a browser automation agent and a compliance tool that uses retrieval over PostgreSQL with pgvector and the Claude API. Each one is described in a case study on the work page, including the decisions and trade-offs.

Who owns the code and the product?

Ownership terms: you own the code and assets on final payment. At handover Jovanni delivers the source code, documentation and access to every service set up for the project, so you are never locked in to Jovanni.

What happens after launch?

After launch Jovanni monitors the first live traffic and fixes issues during the agreed support window of support window. After that you can run the product on your own with the documentation, or continue with ongoing maintenance and new features.

Which time zone does Jovanni work in?

Jovanni works remotely and adjusts working hours to what the client needs, so there is no fixed time zone. Meeting times and the amount of overlap are agreed during the discovery call. Updates are written and asynchronous by default, with calls scheduled when a conversation is faster than a message.