From the idea to an intelligent operation

Six lines of delivery — websites, systems, apps, automation, AI and cloud — each with what is included, typical timelines and how the project runs.

Next Delivery layers

What I can work on

Six concrete delivery fronts — from systems to agents — with the tools that enter each project.

01 / 06

Website design and development

I design and build the whole site — art direction, copy with you, code and launch. No templates: every page comes from what your business needs to say, at the standard of this site.

Landing page: 5 to 10 business days · Company website: 2 to 4 weeks · Site with blog or content area: 4 to 6 weeks

What is included

  • Custom art direction and layout
  • Copy structured with you
  • Next.js development, fast and responsive
  • SEO, structured data and an agent-ready layer (llms.txt and markdown)
  • Launch, domain and analytics
  • Editing handover and 30 days of adjustments

Tools

  • Next.js
  • React
  • Tailwind CSS
  • Figma
  • Vercel
  • Cloudflare
Open service
02 / 06

Software development

When spreadsheets and loose tools stop keeping up, I build the system where the work happens: clear screens for the team, business rules in code and a base ready to grow.

Dashboard or internal tool: 2 to 6 weeks · System MVP: 4 to 8 weeks · API or integration: 1 to 3 weeks

What is included

  • Flow and rules mapping
  • Interface for the team and for clients
  • Database, permissions and login
  • Documented API
  • Deploy, monitoring and backups
  • Documentation for whoever operates it

Tools

  • TypeScript
  • Next.js
  • React
  • PostgreSQL
  • Prisma
  • Docker
  • Vercel
Open service
03 / 06

Applications

Apps that talk to the operation — from the field team's app to the customer-facing product. One codebase for Android and iOS, integrated with the APIs and databases you already have.

Clickable prototype: 1 to 2 weeks · App MVP: 6 to 10 weeks · Store release: +1 week

What is included

  • Mobile flows and interface
  • Cross-platform app (Android and iOS)
  • Login, notifications and offline mode when it makes sense
  • API and database integration
  • Store release
  • Error and usage monitoring

Tools

  • React
  • Expo
  • TypeScript
  • Firebase
  • Vercel
Open service
04 / 06

Automation & Integrations

What today depends on someone copying, chasing or checking becomes a flow that runs by itself — with a person only on exceptions. I use the tools you already have, without replacing everything.

Simple automation: 3 to 7 days · System integration: 1 to 3 weeks · Multi-step flow: 2 to 4 weeks

What is included

  • Current flow mapping
  • Automations between existing tools
  • WhatsApp and email integration
  • Alerts when something breaks the rule
  • A log of what ran
  • Documentation and adjustments

Tools

  • n8n
  • WhatsApp
  • Stripe
  • Supabase
  • Slack
Open service
05 / 06

Artificial Intelligence

AI that works inside the process, not in a loose chat: assistants that know your documents, agents that carry out tasks with defined permissions and MCP servers that connect it all to your systems.

Assistant with knowledge base: 1 to 3 weeks · Agent with tools: 2 to 5 weeks · MCP server: 1 to 3 weeks

What is included

  • Assistant with the company knowledge base
  • Agent with defined tools and permissions
  • MCP server for your systems
  • Skills for the team to use in Claude and ChatGPT
  • Usage logs and human review
  • Cost control per use

Tools

  • OpenAI
  • Claude
  • Gemini
  • LangChain
  • Cursor
  • Python
  • n8n
Open service
06 / 06

Cloud & Infrastructure

The part nobody sees but everything rests on: fast hosting, automatic deploys, a database with backups, professional email on your domain and alerts before a customer notices a problem.

Professional email: 1 to 2 days · Hosting migration: 2 to 5 days · Monitoring and backups: 2 to 5 days

What is included

  • Hosting and domain configured
  • Continuous deploy on every update
  • Database with automatic backups
  • Professional email on your domain
  • Monitoring with alerts
  • Access documentation

Tools

  • Vercel
  • AWS
  • Cloudflare
  • Docker
  • PostgreSQL
  • Redis
  • Grafana
Open service
End of set

How the layers add up

From what the visitor sees to what the agent can access — hire one layer or several. Scroll the list: the section follows the layer you are reading.

Section A-A · layer 01 — Design & Web
  1. 01

    Design & Web

    The first visible layer of the operation: identity, hierarchy and a site that a person — and an AI agent — can read.

    The work starts with what the brand needs to say before anything is automated. I structure the narrative, the navigation and the service pages so a visitor understands what the company does, who it is for and how to start. The same content is marked up for search engines and agents: clear titles, structured data and text that answers real questions.

    • Visual direction and content hierarchy
    • Sites and landing pages in Next.js
    • Metadata, Open Graph and structured data
  2. 02

    Platforms

    Systems built for the operation, with a clear interface and a base that holds the next process without starting over.

    When the spreadsheet or the loose set of tools stops coping, the platform becomes the place where the work happens. I design flows, permissions and screens tied to what the team already does, and leave the architecture ready for agents and integrations later.

    • Applications connected to the operation
    • Interfaces for internal teams and clients
    • A base ready for APIs, data and agents
  3. 03

    Automation

    What still depends on someone copying, chasing or checking becomes a flow that runs on its own, with a person only for the exception.

    I map the process as it is and separate what can leave the team's hands. Automation connects tools that already exist: spreadsheet, email, ERP, WhatsApp, calendar.

    • Map of the current flow
    • Automations between existing tools
    • A trail of what was executed
  4. 04

    AI Agents

    Agents that read the context, choose a tool and carry out one step of the process.

    An agent has a goal, limited access and a rule for what it may do alone. I build agents for service, operations, sales and follow-up — each with a closed scope.

    • An agent with a scope and an autonomy limit
    • Access to the tools of the process
    • A rule for when a person must step in
  5. 05

    MCP & Integrations

    Model Context Protocol as the standard door between the agent and the systems the company already runs.

    With MCP, the system exposes what the agent may read and run. This site publishes a public MCP server with services, products, scenarios and contact.

    • An MCP server for the client's systems
    • Tools with minimum permission
    • Integration with ERP, CRM, APIs and databases
  6. 06

    SEO, AEO & GEO

    Content that can be found on Google and cited by AI agents.

    SEO still counts. AEO and GEO add llms.txt, robots.txt signals and stable facts on MCP so the agent can cite safely.

    • Metadata and structured data
    • Content in answer blocks
    • Signals for agents (llms.txt, MCP, robots.txt)

Next step

Shall we get this built?

Send the brief by email, WhatsApp or the form. I reply with the missing questions and then with scope, timeline and price in writing — no mandatory meetings.

  1. 01Written brief
  2. 02Fixed proposal
  3. 03Deliveries with online previews
Send a brief

or hi@yanmantovani.com · WhatsApp