An AI operations studio · Melbourne

We build AI operations for Australian businesses.

OpsDock designs, builds, and runs the AI side of your business. Installed in fourteen days. Supported for ninety. We work with a small number of clients each quarter.

4
clients per quarter
14
days to live
90
days of joint run
29
skills in the index
The stack

Built on the AI you trust. Wired into the channels you live in.

We build on the models that fit your data policy, then connect them to the tools and channels your team already uses every day.

Models we build on
OpenClawOpenClaw
Nemoclaw
Claude CodeClaude Code
ChatGPTChatGPT
GeminiGemini
Channels we integrate with
TelegramTelegram
WhatsAppWhatsApp
iMessage
SlackSlack
Plus the tools you already use
XeroXero
HubSpotHubSpot
ShopifyShopify
Google WorkspaceGoogle Workspace
Google AdsGoogle Ads
MetaMeta
LinkedInLinkedIn
MailchimpMailchimp
KlaviyoKlaviyo
Okendo
Microsoft 365Microsoft 365
NotionNotion
AirtableAirtable
Monday.comMonday.com
FirefliesFireflies
StripeStripe
n8nn8n
ZapierZapier
SupabaseSupabase
VercelVercel
Services

Three ways AI ops gets into your business.

Most operators start with the middle path. The survey gives you a plan; the install gives you a working system; the run gives you a team that owns it.

Survey

Fixed fee · 2 hours

Map your business. Leave with a plan.

  • Two-hour discovery call with the operator
  • Workflow, stack, and risk mapping
  • A written plan of work, yours to keep
  • No pressure to continue
Most chosen

Install

Fixed fee · 14 days to live

We build the agents and wire them in.

  • Agents, integrations, dashboards, runbooks
  • Deployed inside your environment
  • Human-in-the-loop with full audit trail
  • Live by day fourteen, not theoretical

Run

Monthly retainer · 3-month minimum

We run it with you for ninety days.

  • Joint operation with your team
  • Weekly written ops reports
  • Tuning, hardening, escalation coverage
  • Your team takes the helm by day ninety
How it works

Four phases. Three months. One operator.

01

Survey

Two-hour discovery. We map your business, your stack, and the work you would most like to give to a machine.

02

Build

Fourteen days. We design the agents, wire the integrations, set up dashboards, and document escalation paths.

03

Install

On day fourteen your team gets credentials, runbooks, and a private channel with the operator who built it.

04

Run

Ninety days of joint operation. We monitor, tune, and harden. By day ninety, your team owns it.

Patterns from past engagements

What it tends to look like.

Indicative ranges drawn from past engagements. Your numbers fall out of the survey call, not the website.

DTC brand

8 figures

Returns triage, supplier follow-ups, post-purchase comms.

15 to 25 hours of founder time recovered each week.

Brokerage

30 to 80 staff

Inbound lead triage, document workflows, inspection coordination.

30 to 50% faster routing on new enquiries.

Agency

10 to 25 staff

Client reporting, intake forms, internal QA against playbooks.

8 to 12 hours per team member recovered each week.

Trades and construction

Family-owned

Quoting, supplier comms, job tracking, after-sales follow-up.

Owners back to a 6pm finish inside two months.
What we install

The index.

We've installed most of the items here at least once. Some are off-the-shelf, some are bespoke. None are theoretical.

Talk to us about a specific one
Customer-facing
  • ·Inbound email triage and routing
  • ·Lead qualification and enrichment
  • ·Post-purchase comms sequencing
  • ·Returns and refunds workflows
  • ·Bookings, reschedules, no-show recovery
  • ·Review requests and follow-up
  • ·Support ticket classification
  • ·Knowledge-base and FAQ agent
Sales and CRM
  • ·CRM hygiene and deduplication
  • ·Account research and brief generation
  • ·Outbound sequencing
  • ·Proposal and quote drafting
  • ·Pipeline health reports
  • ·Loss-reason capture
Internal ops
  • ·Weekly written ops reports
  • ·Daily dashboard generation
  • ·Meeting note capture and routing
  • ·Executive inbox triage
  • ·Calendar coordination
  • ·Document drafting from templates
  • ·Internal QA against playbooks
Vendor and supplier
  • ·Supplier email follow-up
  • ·PO generation and tracking
  • ·Invoice extraction and routing
  • ·Quoting from supplier feeds
Bespoke tooling

When off-the-shelf falls short, we build the tool.

MCP servers, connectors, dashboards, agent skills, payment gateways — whatever the job actually needs. Shipped with security and engineering best practices baked in, not bolted on.

Daydeck

Operator dashboard
daydeck.underdogs.dev

A daily cockpit for the metrics, queues, and agent runs an operator actually needs to see before their first coffee. Built when the off-the-shelf dashboards drifted out of sync with the workflows behind them.

Chest Gate

Pay-per-call gateway
chest.sh

x402 payment gates for APIs, agents, and MCP servers. Wallets are managed by Privy so keys never touch our infrastructure, and every request is metered, signed, and auditable.

Principle

Security by default

Least-privilege credentials, scoped tokens, signed requests, audit trails. We assume the agent will be wrong sometimes — and design the blast radius accordingly.

Principle

Built on standards

MCP for tool servers, OAuth and OIDC for identity, x402 for paid endpoints, Tailscale for private networking. Boring choices that age well.

Principle

Yours to keep

Source in your repos, deployed inside your environment, documented for the team that will run it. We are not the dependency.

Daniel Montoya, founder of OpsDock
Daniel Montoya · Melbourne
The operator

Daniel Montoya.

Engineer and founder, twenty years building production systems for businesses that needed to keep running while they were being rebuilt. OpsDock is what I'd hire if I were running your business today.

I take on four clients a quarter. If we're a fit, we'll both know by the end of the first call.

Clients
4 / quarter
Base
Melbourne
Stack
Your own
Ready when you are

Ready to get AI ops into your business?

We build it. We install it. We run it with you for ninety days. Every engagement starts with a scoping call. No templates, no canned decks.

Six short fields: the two workflows you would most like to give to a machine, the stack you run them on, and what good looks like in ninety days. We reply within a business day.