Skip to content
Cedric Kato
Sheet A-000 — Practice of Cedric Kato

Cedric Kato, AI Solutions & Automation Consultant

5+ years · 200+ businesses

I design and build the automations, AI agents and internal tools that run businesses in the background.

Fig. 0 — Plan of a back office that runs itself

Selected work

Products I've designed, built and shipped.

Multi-tenant SaaS, AI utilities, internal tools and consumer apps, each taken from first sketch to live product.

  • Axis sign-in screen: the operations OS for service businesses.
    Fig. 01SaaS · Operationsaxis-ops.app

    Axis — visit live site (opens in a new tab)

    Multi-tenant SaaS operations platform for VA service businesses — team, clients and communications on one control surface.

    • Next.js
    • Vercel
    • Neon Postgres
    • Resend
    • Anthropic API
  • Sortie landing page: your inbox, finally sorted.
    Fig. 02AI · Emailgetsortie.xyz

    Sortie — visit live site (opens in a new tab)

    AI inbox organizer: maps every Gmail sender, classifies them with Claude, then builds the labels and filters so new mail arrives pre-sorted.

    • Claude
    • Gmail API
    • Google sign-in
  • Curriculum Hub overview dashboard showing milestone progress and a lesson sign-off table.
    Fig. 03Internal toolcurriculum-hub-portfolio.vercel.app

    Curriculum Hub — visit live site (opens in a new tab)

    Curriculum operations dashboard with role-based access for content, editorial and voiceover teams.

    Portfolio demo with fictional data.

    • Next.js
    • Role-based access
    • Dashboards
  • Log Pose card catalog showing a filter sidebar and a gallery of One Piece cards.
    Fig. 06Tool · Cataloglog-pose-optcg.vercel.app

    Log Pose — visit live site (opens in a new tab)

    One Piece Card Game navigator: browse, filter and sort the full English card catalog and build tournament-legal decks.

    • React
    • Vite
    • Search & filters

Practice areas

What I do

All services, as a sheet index

How I work

I map the whole building before laying a brick.

I trained as an architect (B.S. Architecture, University of Santo Tomas), and I still work like one. Before building anything, I map the whole system: every tool, handoff, inbox and spreadsheet, and the people who touch them.

Most automation fails because it gets built one fix at a time. Drawing the full plan first is how the pieces end up working together. In 5+ years I've built systems for 200+ US-based businesses across nearly every industry this way.

years building business systems
5+
US businesses supported
200+
full system map before any build
1
  1. 01

    Survey

    I map how work actually moves today: every tool, handoff, spreadsheet and inbox. You get the map in writing before anything is built.

  2. 02

    Blueprint

    A scoped plan: what gets automated, what stays human, what it connects to and what it will cost to run. You sign off before I build.

  3. 03

    Build

    Delivered in stages your team can test with real data, with error handling and logging from day one rather than bolted on later.

  4. 04

    Handover

    Documentation and a recorded walkthrough, so your team can run it and change it. Your accounts, your data, your system.

Contact

Tell me what's slowing the business down.

Optional
Optional

I read every message myself.