Nakao Holdings

Services

Five practices. In every one: a written scope before work starts, and one person accountable from start to finish.

Websites and landing pages

Responsive sites and focused landing pages with clear content, built, tested, and delivered.

What it includes

  • Page structure and copy
  • Responsive design, phone to desktop
  • Accessible, lightweight build
  • Versions in English, Portuguese, or Japanese

What you receive

  • A live site, or one ready to publish
  • Source code and files
  • A short guide to editing content

What it doesn’t promise

  • No guaranteed leads, rankings, or sales
  • No instant delivery: timing comes from the scope

Good first message: Tell us the page’s goal and who it speaks to.

Plan a website

MVPs

A scoped first usable version of your product, with validation criteria agreed before any code.

What it includes

  • Problem and audience map
  • Minimum scope: what’s in, what waits
  • Clickable prototype
  • First-version development

What you receive

  • A working first version
  • Scope document
  • Agreed validation criteria
  • A list of what comes next

What it doesn’t promise

  • Not a production platform with every future feature
  • Validation is measured after launch, not promised

Good first message: Describe the idea and what needs proving first.

Plan an MVP

Apps

A product flow and implementation matched to the platform and scope we agree on — web app or phone app, stated plainly.

What it includes

  • Flows and screens
  • Interface design
  • Development
  • Testing on the devices available

What you receive

  • A web or mobile app as scoped
  • Code and documentation
  • A release checklist

What it doesn’t promise

  • No app-store listing or platform account that doesn’t exist yet
  • Device testing covers the devices actually available

Good first message: Tell us who will use the app, and in what situation.

Plan an app

Marketing campaigns

A creative concept, assets, and copy, with an agreed plan for where it runs and how it’s tested.

What it includes

  • Concept and script
  • Static and motion assets
  • Copy and captions
  • Distribution or testing plan

What you receive

  • Assets in each channel’s format
  • Caption files
  • Editable source files

What it doesn’t promise

  • No guaranteed reach, conversion, revenue, or virality
  • Hooks are hypotheses we test after launch

Good first message: Say what the campaign needs people to understand.

Plan a campaign

Intake and triage automation

Collect, classify, route, and escalate incoming requests — sales, support, and more — with a person in control.

What it includes

  • Request intake
  • Intent classification
  • Collecting missing context
  • Routing to the right queue
  • Handoff to a person when needed

What you receive

  • A documented flow
  • Rules you approve
  • Integration or dashboard, as scoped
  • A human-review plan

What it doesn’t promise

  • No autonomous high-stakes decisions
  • No integration claimed until it’s built and tested

Good first message: Show us where requests arrive today and who answers them.

Plan intake automation

How the work connects

From the first message to delivery, with a person at the review step.

A demonstration of one project moving through five steps. The data is illustrative; step through it or let it play.

Demonstration · illustrative data

Inquiry

“I’d like a website for my bakery, with a menu and a way to order.” The message arrives through the form instead of getting lost between channels.

What you receive: A written summary of what we understood.

Illustrative project and messages. Nothing on this page is sent anywhere.

Your next step starts with a conversation.

Tell us what you want to build in a few lines, in English, Portuguese, or Japanese.

Start a project

Nakao Holdings’ project guide

Mioミオ

Mio runs on hand-written rules, no AI: nothing you type leaves this page. For any real decision, a person answers.

Nakao Holdings