We build on the stack we run.
If you need something specific built, a capability on top of ArcGrid, or agent software from scratch. This is the engagement. We scope it, price it, build it, and hand it over running.
Start from where you are.
Not every client starts with the full platform. Some need a specific capability built on top of it. Some already have infrastructure and just need agents that run on it. Custom Build covers both.
You're already on ArcGrid.
You run the Surface and need something built on top: a custom pack for your vertical, an integration with a tool we don't cover out of the box, or a workflow configuration specific to how your firm operates. We build it inside the platform you already have, using the same agent architecture and approval gate patterns everything else runs on.
You need agent software. We build it.
You don't need the full Surface. You have a specific problem and you want purpose-built software that solves it. We scope the build, architect it on the ArcGrid stack, and hand it over running on your infrastructure or ours. You own the output. No platform subscription required. Just a well-defined build engagement with a fixed scope and a clear handoff.
If it's recurring, documented work, it's build territory.
Every build uses the same primitives we run on production: the same agent architecture, the same Vault and memory layer, the same approval gate patterns. Your custom build is not a one-off. It runs on infrastructure we maintain.
Vertical configurations
Industry-specific agents, document understanding, and recurring workflows assembled into a complete working practice for your domain. Installed directly on the Surface you already run.
Connect what you already have
Structured connections between your existing tools and data sources and the Grid. Work stops living in silos. The agents learn your systems without you rebuilding your stack.
Purpose-built multi-step processes
Specific, repeatable tasks that need an agent sequence: research, drafting, review, approval, dispatch. Scoped to your exact process, not a generic template.
End-to-end flows that run on triggers
Pipelines that fire on schedules, external events, or human approval gates. Nothing moves without the right conditions met. Every step is logged and auditable.
Structured extraction and loading
Pull data from documents, APIs, or external systems, transform it to your schema, and load it into your Vault or wherever it needs to go. Reliable, repeatable, observable.
Visibility for your end clients
Web-based views that show engagement status, deliverable progress, and relevant outputs to the clients you serve. Branded, scoped, and connected to the work already happening in the Grid.
Every build starts with a scoping engagement.
You describe the problem. We map it to a build: what gets built, what stack it runs on, what the handoff looks like. From that we produce a scope and a price. Fixed-scope, fixed-price or milestone-based, depending on the complexity. No retainer required to start. The scoping engagement is the first step, not a commitment to the full build.