FOUNDER-LED · KANSAS CITY + REMOTE

Direct technical accountability from first scope to final handoff.

Obtuse AI exists to turn frontier tools into systems people can understand, operate, verify, and own. The studio is built around hands-on architecture and implementation—not a sales layer separated from the person responsible for the work.

Start a direct conversation Inspect the work

01 Why Obtuse exists

AI capability is abundant. Coherent implementation is not.

Teams can access models, copilots, agents, and automation platforms within minutes. The difficult work begins after access: choosing the right job, redesigning the workflow, connecting data and systems, defining permissions, measuring performance, and transferring operational ownership.

The Obtuse portfolio was built as an operating laboratory for that work. Across local AI, autonomous engineering, forecasting, simulation, creative production, and governed agents, the same architecture keeps returning: explicit jobs, visible evidence, bounded authority, independent validation, and human-owned decisions.

That is the value offered to clients. Not generic AI awareness. A direct path from opportunity to owned capability.

02 Ownership and data handling

No hidden dependency. No stolen authority.

Specific terms belong in the engagement, but the operating doctrine is stable.

Custom code

Ownership and licensing are stated in the proposal. Client-specific code and deliverables transfer as agreed; third-party and public-source licenses remain explicit.

Client data

Client information is used only for the agreed work. Data paths, model providers, retention, and any training exposure are disclosed before implementation.

Credentials and authority

Production credentials and consequential permissions remain controlled by the client or an explicitly named human operator.

Ongoing access

Any maintenance access, monitoring, or support window is documented. Obtuse retains no silent production authority.

Acceptance evidence

The proposal names how important work will be reviewed: tests, demonstrations, artifacts, checkpoints, or human acceptance.

Handoff and support

Documentation, deployment access, operating boundaries, and the included support period are made clear before delivery.

03 Engagement expectations

What happens after you contact us.

The first exchange determines fit and the next useful decision. Paid discovery, an assessment, a pilot, or a direct build is proposed only when it matches the uncertainty.

01
Contact
Send the pressure, opportunity, product idea, or current AI system.
02
Fit
We clarify the job, constraints, decision owner, and whether Obtuse is the right builder.
03
Scope
You receive deliverables, boundaries, checkpoints, ownership, acceptance evidence, investment, and timing.
04
Build
Working paths and proof are reviewed throughout—not saved for a final reveal.
05
Handoff
You receive the system, access, evidence, documentation, and a clear support boundary.