§ CUSTOM WORK · DMA-SVC-001
We still take
a few
custom builds.

DemanualAI · Services · 2026

§ 01 — The 10%

Most of what we do
is product.

But some businesses need something specific enough that it doesn't fit a template: a custom model, a system we integrate deeply, or an automation Flows and Dataviz do not cover.

We take a small number of those each year. The founder is the lead engineer on every one. If it isn't a fit, we say so on the first call and point you at someone better placed.

The person who scopes your project is the person who builds it.

§ 02 — Scope

Selective by
design.

What we take
  • Deep WhatsApp automations that go beyond standard Flows templates
  • Database, ERP, and operational reporting systems that extend Dataviz
  • Custom AI models where the data and success metric are clear
  • Internal tools that connect messy business systems into one working loop
  • Ongoing maintenance for systems we built or audited and trust
×What we don't take
  • ×"Add AI to our product" with no specific problem defined
  • ×Pure chatbot wrappers that cannot take action
  • ×White-label work that hides who built it
  • ×Anything that needs a 30-person team to execute
  • ×Anything we would not be proud to demo
§ 03 — How custom pricing works
1
Free first call to check fit
Fixed
Scope and quote before the build
Few
Custom builds accepted each year
§ 04 — How to start

One call.
Thirty minutes.

01Book the first call. Free, thirty minutes, and the founder will be on it.
02We tell you honestly if we can help. If it fits Flows or Dataviz, we will say that. If it needs custom work, we will say why.
03We scope the smallest useful version. One workflow, one data source, one report, or one operational loop.
04Build. Weekly demos from week one. You see working software, not status theatre.

The first call is thirty minutes. One of us will be on it — not a sales rep, not a coordinator. We'll tell you honestly whether we can help and what it would look like.

If we take the project, you'll know our names, our number, and who is responsible for the system after launch.