Judge: section order, proportion, hierarchy, copy placement. Imagery, motion, and polish are later passes. Dashed blocks mark where imagery lands.
Blue = AI-generated. Neutral = coded / authored / real. Every imagery slot and motion carries its medium + framework so the build intent is explicit.
Public pricing on every Custom Build tier. No 'contact us' for first-step buyers.
Start with a $4-8K Operations Map. See how you run mapped and your builds priced before you commit to one.
constants = messaging.md pricing-hook language, true at every rung · same items run in the closing ticker (bookend)
Systems mapped, SOPs documented, builds scoped — yours to keep whether or not you build with us.
A fixed-scope systems-and-process engineering engagement: engineers embed, document how the buyer's operation actually runs, then deliver a priced build plan.
The Map: systems inventory + process flows + written SOPs + priced build plan
- The Map delivered within 2 weeks of kickoff
- Build plan includes effort estimates, prerequisites, and fixed pricing for next-step Sprint or Custom Build
- All Map artifacts are the buyer's to keep, whether or not they build with Actify
- Buyer signs off on the Map or surfaces gaps for revision
Operators taking the lowest-friction first step — systems mapped and builds priced before committing to a build.
One named build shipped to production in 4 weeks.
One named system shipped to production
- System shipped to buyer's production environment by week 4
- Pre-agreed functional checklist signed off
- Architecture documentation delivered; deployed instance licensed to the buyer
- 30-day support window starts at production ship
Operators with a single named build to ship to production — under the threshold that needs board or partner sign-off.
Always the buyer's outright: their data, their configurations, and their business documentation (the Map, process flows, SOPs) — whether or not the engagement continues.
The flagship Custom Build engagement.
- Full system architecture and design
- Production-ready implementation (not demo code, not sandbox)
- Deployment to buyer's production environment
- Architecture documentation delivered; deployed instance licensed to the buyer
- System shipped to buyer's production environment within 8 weeks
- Pre-agreed acceptance checklist signed off
- Functional + performance metrics validated
- Architecture documentation delivered; deployed instance licensed to the buyer
- 30-day support window starts at production ship
Operators whose pain doesn't fit a single Sprint — full-scope builds, usually after an Operations Map.
Fractional attaches to every build — the Operate phase is part of the engagement, not an option
Your fractional AI engineering, on retainer. The engineers who built your system stay embedded to run, maintain, and extend it as your operation changes — the senior AI capability an SMB can't justify hiring full-time.
Ongoing maintenance + iteration on shipped builds
- Monthly check-in delivered
- Agreed-upon deliverables for the month complete
- Buyer can cancel at any time with 30-day notice
Operators who want the team that built the system to stay on to run and extend it — without staffing an in-house engineer.
ranges canonical: Map / Sprint / Custom Build from services/actify-custom-builds/ offer.md, Fractional AI Engineering from messaging.md pricing hooks · no contact-us gating, ranges always shown · What it is / Deliverables / Acceptance criteria + the callout subs transcribed VERBATIM from the service file — copy LANDED (dddbc49) · Who it's for GAPPED — no canonical line in offer.md, founder draft pending