Your SaaS, usable by AI agents in two weeks.

Soxoa builds the production MCP server, sign-in for agents, and directory listings that let ChatGPT and Claude users work in your product. Built by John Arndt, who already runs them on Soxoa's own products. Fixed scope, and the code is yours.

AI consulting for other teams: AI consulting in Sacramento · AI consulting in the Bay Area

How an AI assistant reaches your productA user's assistant, such as ChatGPT or Claude, signs in through your product's agent sign-in, calls tools on an MCP server, and the server calls your existing API. The MCP server is also listed in the registry and directories. The reviewer marks the sign-in, the server and the listings as the part Soxoa builds in ten working days.AI assistantChatGPT · Claude · agentsAgent sign-inOAuthMCP serverTools your users needA scope on every toolConfirm before it spendsListedRegistryDirectoriesYour existing APIAWe buildthis in tenworking daysDrawingAgent access, as builtScopeInside the cloud

Already running on Soxoa's own products.

Each of these is a live MCP server you can connect from ChatGPT or Claude today. Yours is built the same way, in your repository, in ten working days.

Not a SaaS? Four engagements for working AI.

Start wherever your organization actually is. Every engagement stands alone and ends with a written record and a named owner on your side for the next decision: a working build when the evaluation clears the bar, an honest stop when it does not.

  1. AI Readiness Assessment

    “Where are we, honestly?”

    A self-scored survey of ownership, workflows, data and tools, people, and governance. It names your weakest dimension and the engagement that fits, including the case where the right move is to buy nothing yet.

    See which readiness gap to investigate before committing budget.

    About five minutes. Free. Runs in your browser; answers are not stored.

    Take the assessment
  2. Live Build Workshop

    “Can my team actually do this?”

    John and the people who do the work build one automation together, on approved examples of their real work, in one day. The team sees every decision, including what gets rejected and why.

    Leave with one tested automation and a team that knows how to run and review it.

    One working day on site or remote, plus a short preparation call.

    Plan a workshop
  3. AI Build Sprint

    “Get the important one into production.”

    A fixed-scope sprint that takes one to three workflows from mapped to operating in your environment. Options are tested on real examples before anything is installed, a named person reviews what needs judgment, and everything is documented for handoff.

    If the evaluation passes, put the workflow into operation with an owner and human review path.

    Days to a few weeks, depending on the workflows. Scope and price agreed before work begins.

    Scope a sprint
  4. Fractional Chief AI Officer

    “Who owns AI here, month after month?”

    John joins your leadership rhythm as the accountable AI lead: setting priorities, deciding on tools and vendors, governing use, overseeing delivery, developing the team, and reporting what changed each month.

    Give leadership a current record of what runs, what was declined, and who owns the next decision.

    Monthly engagement. Scope and price agreed before work begins.

    Discuss a fractional role
John Arndt, founder of Soxoa

You work with the person holding the pencil.

John Arndt runs every engagement himself. He spent more than a decade in AI, cybersecurity, fraud and risk, privacy, payments and enterprise software, where a wrong answer costs real money. Soxoa also builds and runs AI software of its own, in public.

Software Soxoa builds and operates. Products, not client case studies.
ProductWhat it does
AnnotatedKeeps a passage, video moment, or podcast clip together with your commentary and its original source.
MentionedOnTracks how AI assistants describe and recommend local businesses.
IntakraTurns public buying signals into a reviewed why-now brief for sales teams.
DokyumiExtracts structured data from business documents, with review before it lands.
PortravoTurns construction plans into reviewable quantities and estimates priced against dated local benchmarks.
PostedlyLets an AI assistant prepare physical mail and faxes, with the sender reviewing every detail before payment.

General notes. They apply to every sheet.

  1. Build it on the real work

    A demo on clean sample data proves nothing. Every option is tested on approved examples of your actual work before anything is installed.

  2. Ask to see the tests

    Ask what the system was tested on, where it failed, and what changed. The people who own the workflow should understand the evidence behind the decision to put it into operation.

    What to ask before buying an AI agent

  3. Some work should stay manual

    Rare cases, judgment calls, and anything where a mistake costs more than the time saved. Marking those early is part of the job, not a failure to sell.

  4. A named person signs off

    Where output reaches a customer, a record, or a decision, someone accountable reviews it. The review path is designed first, not bolted on after.

  5. Your team can run it without us

    Operating notes, access, and an internal owner are deliverables. If the system only works while we are in the room, it is not finished.

Bring the workflow that slows you down.

Thirty minutes with John. You describe the bottleneck; he tells you what he would mark up, what he would leave alone, and whether Soxoa is the right fit.