00 ·Engagements · Three shapes
Three shapes. One builder.
Starter, Build, Embed. Every engagement ships a runnable system on your stack. No deck-only handoffs. No subcontractor chains. No retainer required.
$4,950
Working system on your stack by Friday.
See details$15K–$35K typical
Your workflows, end to end, in production.
See details$3K–$5K / month
AI as your operating infrastructure.
See detailsEvery shape, including the Starter, ships a runnable system on your stack. The line that separates Praxis from generalist AI consulting and the line that holds the brand together end to end.
01 ·Starter
Starter. One week. Working system by Friday.
One week. We install our Merlin layer on your stack and ship a starter workflow by Friday — your team uses it Monday morning. Alongside the system you receive a systems map of where AI belongs in your operations, a prioritized opportunity list, and a one-page build recommendation for what to ship next.
The system is the smallest meaningful workflow from the systems map, running in production by end of week. Bound by design — big enough to feel, small enough to ship in a week without compromising the strategy work.
New-lead intake routing rule.Form submission lands in your CRM with the right owner, the right tag, and a Claude-classified urgency. Replaces the manual "who picks this up" Slack thread that runs every morning.
Scheduled scrape feeding a Slack digest. Daily Apify run pulls from your watch list, Claude summarizes the signal worth reading, your team gets one digest in #signal-feed at 8am instead of fifteen tabs at 11pm.
Cowork project with two or three skills wired to your team's data. A working department workspace where your team can run "show me last week's churn signals" or "draft the weekly client update" with Claude using your live data, not pasted screenshots.
MCP integration plumbed into your Claude environment. A real data source (Airtable, Notion, Stripe, your DB) connected to your team's Claude Desktop or Cowork projects so the model reads the live state, not stale exports.
You leave the week with a working system, a clear-eyed read on where AI belongs in your operations, and a recommendation you can use whether or not we keep building.
STACK-NATIVE·FIXED PRICE·NO RETAINER·NO DECK·WORKING SYSTEM BY FRIDAY
02 ·Build
Build. Your workflows, end to end.
Fixed-price, fixed-scope implementation of your production workflows, end to end. We own design, build, integration, and handoff. You receive a runnable system, a runbook your team can operate without us, a handoff session, and a 30-day support window for fixes and tuning.
This is the core Praxis offer. Unlike the Starter system, a Build covers the full surface of several workflows: every input, every routing decision, every integration the system depends on, every edge case the team needs handled.
Every input.The form, the inbound email, the upload, the API webhook, the scheduled trigger. Whatever feeds the workflow, it's wired.
Every routing decision. Where the workflow branches, what the model classifies, when a human gets paged, what gets auto-resolved. Specified, tested, monitored.
Every integration. Your CRM, your project tracker, your Slack, your storage, your finance system. Plumbed so the workflow reads and writes against the live state of your business.
Every edge case the team needs handled. The retry logic, the dedup rules, the manual override path, the audit log, the failure alert. Production behavior, not demo behavior.
Pricing is set after a Starter or a free scoping call, sized to workflow complexity and integration surface. Most SMB-tier Builds land between $15K and $35K. Complex mid-market Builds with deeper integration land between $50K and $75K.
03 ·Embed
Embed. AI as operating infrastructure.
Monthly retainer at $3K–$5K per month for ongoing build and iteration across your workflow portfolio. For clients running two or more Praxis-built systems who need continuous design partnership instead of project-by-project re-engagement.
We allocate a defined block of weekly hours against a rolling backlog you set together. Limited concurrent Embed engagements to protect quality and response time. Best for operators treating AI as core operating infrastructure, not a one-off project.
Two or more workflows in flight. A single Build is the wrong unit when your portfolio is moving on multiple fronts at once. Embed plays the long game.
Continuous tuning matters more than building the next thing. A workflow that's been running for three months almost always needs adjustments the Build window didn't anticipate. Embed catches them as they surface.
AI is core operating infrastructure, not an experiment. Your business runs on these workflows. They need an accountable design partner, not project re-engagement every six months.
Embed is not a hosting or support contract. It's design partnership. The output is the same shape as a Build: working systems, runbooks, and the kind of design judgment that only shows up when one builder owns the surface for a long stretch.
04 ·FAQ
Common questions.
Q1How is Build pricing determined?
After a Starter or a free scoping call, we size the Build to workflow complexity and integration surface. SMB-tier Builds typically land between $15K and $35K. Complex mid-market Builds with deeper integration typically land between $50K and $75K. The price is fixed before you sign.
Q2What if I need more than one workflow built?
Two paths. If the workflows are independent, run them as sequential Builds (the second one prices faster because Praxis already knows your stack). If you have multiple workflows in flight at once and want continuous design partnership, Embed is the right shape.
Q3Do you work with my industry?
Praxis serves SMB owners and operators across services, professional services, e-commerce, and specialty operations. Deep familiarity with legal and cybersecurity (data breach response, intake automation, case evaluation), specialty retail and fashion, interior design and architecture, real estate technology, and creative production. We turn down enterprise $100M+ and heavily regulated verticals (healthcare, defense) unless the work is inbound and the fit is clear.
Q4What happens after the engagement ends?
A Starter ships with the system, the systems map, and a one-page recommendation. A Build ships with the system, the runbook, a handoff session, and a 30-day support window. After the support window, you can extend into Embed or pick up the next Build when you're ready. Praxis does not lock you into ongoing fees you don't need.
Q5Do you sign NDAs?
Yes. Mutual NDA is the default for any engagement that touches client data, customer records, or proprietary workflows. We sign yours or use ours.
Q6Do you work fully remote?
Yes, by default. Praxis is async-first. Weekly check-ins via Google Meet or Slack when the build cadence calls for it. If your engagement benefits from on-site time, NYC and the Northeast corridor are easy; further than that is a per-engagement call.
Q7Is the website really a Praxis demo?
Yes. The animated workflow diagrams, the choreographed reveals, the integrated systems quality, the way Cowork and MCP power the case studies, all of it is the same kind of build we do for client engagements. The website is the most visible Build in the Praxis portfolio.
Get started.
One week. Working system by Friday. Fixed at $4,950.
BeginOr read what Praxis builds → Recent work