// crate.works / v1
Stop renting software.
Start deploying engines.
Custom AI engines that run your operations. Deployed in weeks. Better every month.
→ Every engine signed by an accountable builder.
~/crate-works — claude
// The engines we deploy
See the full library →- Growth Engine
Outbound, content, and referral systems that compound.
- Operations Engine
Workforce visibility, scorecards, scheduling, margin monitoring.
- RFP Engine
Opportunity discovery, qualification, draft generation, win-loss tracking.
- Proposal Enginealpha
Generation, customization, and follow-through for sales orgs that draft too slowly.
- Recruiting Enginealpha
Sourcing, screening, and pipeline operations for high-volume hiring or specialized roles.
- Research Enginealpha
Discovery, synthesis, and decision support for teams making informed bets.
// Where the engines run
Logistics
Multi-territory logistics operator
Healthcare
Regional healthcare platform
Hospitality
Multi-location catering operator
PE Portfolio
PE-backed services rollup
Professional services
B2B professional services firm
Staffing
High-volume staffing operator
Logistics
Multi-territory logistics operator
Healthcare
Regional healthcare platform
Hospitality
Multi-location catering operator
PE Portfolio
PE-backed services rollup
Professional services
B2B professional services firm
Staffing
High-volume staffing operator
01 The problem
Your business is too specific for SaaS.
Too small for a dev shop.
The software market gave you two choices: configure a generic platform until it almost fits, or pay an enterprise dev shop seven figures to build something custom. Most operators pick option one, spend a year in implementation, and still use a fraction of what they’re paying for.
We built Crate Works for the third option. Custom operational engines, designed around how your business actually runs, deployed in weeks instead of quarters, and improved continuously instead of frozen at launch.
Not configured. Built. Not licensed. Owned. Not finished. Evolving.
02 How we work
We don’t deliver decks.
We deliver systems.
- 01
Outcome scoping
Two to four weeks with your operators, your data, and your real workflows. We scope the engine around the business outcome, not the tech stack.
- 02
Custom build
We ship working software, usually within weeks. AI-first, often headless, automation where it belongs and human-in-the-loop where it doesn't.
- 03
Continuous evolution
AI systems atrophy. We stay engaged — refining, monitoring, extending — so the engine gets better the longer you run it.
// Deployed in weeks
Week 1
Scoping
Operators, data, workflows. We map the outcome and define the engine.
Week 2–5
Build
Working software in your environment. AI-first, your stack, your data.
Week 5+
Live + Iteration
Engine in production. Continuous improvement begins on day one.
// What “better every month” means
New capabilities shipped as your workflows evolve and the work surface area expands.
Performance monitoring so you know what the engine is doing and what it’s worth.
Model and tooling upgrades integrated as the AI landscape moves underneath you.
Workflow refinements based on what your operators are actually hitting.
03 The Builders Guild
Operators backing
every build.
Crate Works is a guild of operators, founders, and technologists who design and stand behind every engine we deploy. Every implementation is signed — one builder accountable, the Builders Guild behind them.
Ben Carcio
Founder, Operator, Builder
Founder of PromoBox. Operator and builder. Signs Growth Engine and RFP Engine.
View profile →
Joseph Bracken
Founder, Operator, Builder
Multi-unit operator. Built and runs FedEx territories and a regional healthcare platform. Signs Operations Engine and Growth Engine.
View profile →
// engage
Tell us what your business
actually runs on.
We work with a small number of operators at a time. If you’re running a mid-market or PE-backed company and you know AI should be changing how you operate, let’s talk about what that looks like for you.
