01
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.
FOUNDER-LED · KANSAS CITY + REMOTE
Direct technical accountability from first scope to final handoff.
Obtuse AI exists to turn difficult ideas into technology people can understand, operate, and own. The studio is built around hands-on product judgment, design, architecture, and implementation—not a sales layer separated from the person responsible for the work.
01 Why Obtuse exists
Powerful tools are abundant. Coherent systems are not.
Anybody can assemble a stack of services. The difficult work is deciding what deserves to exist, designing the experience, engineering the critical path, connecting the data and infrastructure, applying intelligence where it earns its place, and making the whole machine operable.
The Obtuse portfolio is the operating laboratory for that work. Across applications, distributed systems, local AI, autonomous engineering, forecasting, simulation, creative production, interactive 3D, defensive architecture, and active game development, the same standard keeps returning: explicit jobs, visible control, relentless testing, and human-owned decisions.
That is the value offered to clients: one direct path from a hard idea or broken operation to technology with teeth.
02 Ownership and data handling
No hidden dependency. No stolen authority.
Specific terms belong in the engagement, but the operating doctrine is stable.
02
Client data
Client information is used only for the agreed work. Data paths, model providers, retention, and any training exposure are disclosed before implementation.
03
Credentials and authority
Production credentials and consequential permissions remain controlled by the client or an explicitly named human operator.
04
Ongoing access
Any maintenance access, monitoring, or support window is documented. Obtuse retains no silent production authority.
05
Acceptance evidence
The proposal names how important work will be reviewed: tests, demonstrations, artifacts, checkpoints, or human acceptance.
06
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. Discovery, an assessment, a sprint, or a direct build is proposed only when it matches the job.
- 01
Contact
Send the pressure, opportunity, product idea, broken workflow, or current 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 criteria, investment, and timing.
- 04
Build
Working paths are reviewed throughout—not saved for a final reveal.
- 05
Handoff
You receive the system, access, documentation, and a clear support boundary.