47 agents across every department, pre-loaded for the trades.
Log in. Pick a workflow. Done.
AFC is self-serve AI for contractor operations—credits fuel the agents, with knowledge pre-loaded across workspace categories. You log in, pick a workflow tile, and agents work. Claude, GPT, and Gemini underneath one credit system—no custom build required to start.
- Log in. Pick a workflow. Done.
- Claude, GPT, and Gemini—one platform for runs
- Pre-loaded for contractor operations; category tabs on the hangar
Hangar · category tabs · workflow tile · run
Horizontal category nav plus optional Run / Build / Deploy—then a Run tile opens the composer and live run column on its own route.
1
Library collections
∞
Saved runs to reuse
What AFC is — at a glance
Who it is for
Residential and commercial contractors who need operations that keep moving—not another product you spend all day clicking through.
What you get
Self-serve AI for contractor operations: workflow tiles on the hangar, agents grouped in workspace categories behind horizontal tabs, and Run / Build / Deploy lanes when you need to narrow the list.
How you start
No custom build required to start. Sign in, land on the hangar, choose a category tab, open a tile—Run loads the contractor composer with prompt, model, and live run column.
Inside the app
Same shell you get when signed in—start at the hangar with category tabs, then projects, library, or history.
Hangar · workflow tiles
Home is the catalog: horizontal category tabs, lane filters, and one route per agent—tiles first, not buried menus.
OpenWorkspace shell
Run agents open the contractor composer on their own page; Build and Deploy use the same shell with lane-specific surfaces as they grow.
OpenProjects
Group work by job, phase, or campaign so drafts and context stay where your crew expects them.
OpenLibrary
Brand references, photos, and notes the agents can pull into runs.
OpenHistory
Reopen runs, compare wording, reuse what worked—nothing good lost in a tab graveyard.
OpenSettings
Profile, workspace preferences, integrations, and models in one place.
OpenWhy workflow tiles—not another tool to operate
47 agents. One platform. Your trade.
Agents across workspace categories—workflow tiles instead of a sidebar of disconnected features. Every card opens that agent’s route so context stays put.
Automations move data. Agents make decisions.
Complexity stays under the hood; you pick outcomes and review. Brand and job context live in Library and Projects so outputs stay aligned with how you operate.
Their dashboard is a reading assignment
Yours shows work already done. Group work by project, revisit History for winning lines, and ship when you—not a buried queue—say so.
Example workflow runs
- Post-job thank-you + review request email after a big residential close.
- Seasonal tune-up push: subject lines, SMS snippets, and a simple landing blurb.
- Commercial bid follow-up: polite check-in and one-page capability summary.
- Hiring blurb for field leads: Craigslist / Indeed copy with safety-first tone.
- Project spotlight for social: before/after caption and hashtag set.
Trades we had in mind
Pre-loaded for the trades—pick a tile that matches the work, not a blank chat.
- HVAC & mechanical
- Electrical
- Roofing & exteriors
- Concrete & flatwork
- Remodel & GC
- Restoration
- Landscape & hardscape
From login to a finished run
- 1
Log in
Create your account and step into the workspace—see the hangar and workflow tiles without a discovery call gate.
- 2
Pick a workflow
Scan category tabs on the hangar, optionally filter Run / Build / Deploy, then open the tile that fits the job.
- 3
Agents run it
Credits fuel workflow runs. Claude, GPT, and Gemini sit behind one credit meter—review results in History and refine from there.
Questions owners ask before they pick a workflow
Do I need a marketing or IT seat to use this?›
No. You describe the job in plain language, pick a workflow tile, and review what comes back. Operators and owners are the intended users.
Where do drafts and runs live?›
Runs land in History; attachments and context follow the workspace and agent you used. Projects and Library sit in the same shell as the hangar.
Can my team share a workspace?›
Access follows your organization sign-in. Share context from the Library and hand off drafts without losing thread.
Which models power the agents?›
Claude, GPT, and Gemini run underneath with one credit meter—so you are not stitching together separate vendor accounts for the same run.
Power lines we build around
Plain-language briefs
Short bullets beat a perfect brief. You are not auditioning for a slide deck—you are steering a workflow.
A toggle is not a team
Agents handle structured work; you approve. Saved runs beat lost browser tabs when the season gets busy.
Brand context on tap
Library items travel into runs so tone matches how you show up on site.
You sign off
Review before anything ships. Nothing goes out until you say so—built by contractors, tested on real jobs.
Automations move data. Agents make decisions. Platforms run companies—when the interface gets out of the way. Pick residential remodels, commercial bids, or service pushes; the workflow is the same: log in, choose a tile, review work already done.
Ready when you log in: category tabs on the hangar, library context on tap, history for everything you already shaped—without stitching five vendor logins for one job.