private to your business · enforced in the database
Annual replacement at parity if you bought the equivalent tools and services separately. Custom-building this one feature alone would land in our Large build band ($80k–$180k). Source ladder + per-line citations on methodology .
Concretely, what you get
- Materials used at SKU level.
- Roof dimensions, pitch, configuration.
- Neighborhood + ZIP cross-reference.
- Weather conditions at install.
- Crew composition + time on job.
- Customer demographics (where you capture them).
- Warranty terms + 5-year callback log.
- Powers: per-neighborhood website pages, authoritative claims in copy, Pricing Confidence signals, Insurance Toolkit comparisons.
The shelf-of-tools this one offering removes
Categories, not brand names — pricing benchmarks observed from public pricing pages, agency proposals, and freelance rates current to the year. Every range is backed by a line-by-line worksheet you can audit once your trial is live.
| What you'd otherwise buy | Type | Typical price |
|---|---|---|
| Nothing in market — this is a Homericly invention | Build | n/a |
What you'd pay elsewhere vs. what this costs you here
Vendor ranges observed from public pricing pages and agency proposals, current to the year. Full source worksheet shared with you once your trial is live.
What it adds to your business in dollars
Competitors using generic AI content cannot make claims like "We installed 14,800 sq ft of GAF Timberline HDZ in {neighborhood} over the last 3 years with a 0.2% callback rate." You can — because the data is yours, and the platform tracks it for you.
Three or four moves. Then you walk away.
You: Run jobs through Crew Day Pack.
System: Every completion feeds the engine automatically.
You: Watch your marketing copy get more specific.
System: The Writer + Brand agents draw on your evidence by default.
The outcomes this feature feeds into
Before you ask
Who can see this data?
You. Your team. That’s it. Static-checked at the CI level: any query against this table without your organization_id predicate fails the build. Even Homericly staff cannot read raw job data without impersonation — and impersonation is audit-logged with a banner you see in your own log.
How does this fill in if I just signed up?
It starts at zero and accumulates as you run jobs through Crew Day Pack. Within 90 days you have meaningful per-neighborhood + per-material claims; within a year you have the full library.
Can I import historical jobs?
Yes — CSV import of historical jobs at provisioning seeds the engine. Most clients have 1–5 years of past jobs we can map into the schema during migration.
What if my system has a callback that wasn’t logged?
Manual entry surface in the portal. The engine prompts you on jobs older than 90 days to confirm "any callbacks?" so the data stays honest.
Can I share the data with a contractor I subcontract to?
Yes — granular share controls per organization. You can grant read-only on a per-job basis, audit-logged.
See every closed job turn into a private data asset only your business can use.
Then compound the work you already did.
No credit card. No strings. We stand the whole platform up on a subdomain alongside your existing site so you can compare the numbers directly — leads, bookings, ticket size. The Standard guarantee covers cancellation between day 90 and day 180 at full refund.