Files

T

TNB 8f4ed8a306 docs: TallyFlow Scout marketing + Edge/Print/Capture feature refresh

Review tallyflow-assets-iot (TallyFlow Scout v0.5.3): Collect, Verify,
Locate with Edge remote reader / offline CSV locate. Clarify Scout does
not replace Core Assets. Refresh Edge, Print parent-container and multi-
unit identity notes, Capture share/offline/barcode notes, architecture,
use cases, capabilities, and website drafts after src/ repo pulls.

2026-07-27 15:59:32 -04:00

3.7 KiB

Raw Blame History

Website Build Suggestions – First Version (Grok Build)

Date: June 25, 2026
Purpose: Recommendations for building the initial version of tallyflow.com using the marketing content created so far.

1. Overall Site Structure (Recommended)

Proposed top-level navigation:

Home
Products (or Solutions)
- TallyFlow Core
- TallyFlow Capture
- TallyFlow Edge
- TallyFlow Scout
- TallyFlow Print
Use Cases / Solutions
Case Studies
Resources / Blog
Contact / Demo

Alternative (simpler first version):

Home
Capture (stand-alone focus for now)
Solutions (Freight Claims, Manufacturing QC, etc.)
Case Studies
Contact

2. Priority Pages for First Version

High Priority

Homepage – Hero + value proposition + social proof (mini case studies or logos)
TallyFlow Capture Product Page – Core offering right now
Freight Claims Solution Page – Strong commercial angle with Madix proof
Manufacturing Quality Control Solution Page – Broad use case
Case Studies Hub – Full case studies + mini case studies section

Medium Priority

Barcode + Photo Use Cases (blog post)
Individual mini case study pages or a “Customer Stories” grid
Resources / Blog landing page

3. Content Recommendations

Use These Drafts

Freight Claims → Turn the solution page draft into a dedicated /solutions/freight-claims page
Manufacturing QC → Good as either a solution page or blog post
Barcode + Photo Use Cases → Best as a blog post (top-of-funnel)
Mini Case Studies → Create a “Customer Stories” section on the homepage or a dedicated page with 3–4 featured stories + “View all” link
Full Case Studies (Madix, Alice & Olivia, Network of Hope, etc.) → Build a proper /case-studies section

Messaging Angles to Emphasize

Visual proof for freight claims and quality issues
Barcode + photo combination (unique differentiator)
Real customer results (Madix = tens of thousands of photos/week)
Cloud + mobile + rugged hardware flexibility
Time savings and reduced administrative burden

Homepage: Feature 4–6 mini case study cards (Madix, Babbitting, Salter, Hi-Tech, MKB, Tucor)
Freight Claims page: Lead with Madix story
Case Studies page: Mix of full case studies + mini case studies grid
Consider adding logos (with permission) once relationships are confirmed

5. Technical / UX Suggestions

Make the Capture product page the strongest right now (it has the most supporting content)
Ensure mobile experience is excellent (many use cases are field-based)
Include clear CTAs on every page: “Request Demo” and “Start Free Trial”
Plan for future expansion into Core, Edge, Scout, and Print (keep navigation flexible)
Use consistent tagging/categorization language across the site

6. Next Steps (Recommended Order)

Build Homepage with strong hero + mini case study highlights
Build TallyFlow Capture product page
Build Freight Claims solution page (highest commercial intent)
Create Case Studies hub page
Publish 1–2 blog posts (Manufacturing QC + Barcode + Photo Use Cases)
Add individual full case study pages as they are finalized

7. Open Questions for the Team

Should Freight Claims be a top-level “Solutions” page or live under Capture?
Do we want a dedicated “Industries” section (Manufacturing, Retail/Fixtures, Agriculture, etc.)?
How much emphasis should we place on the old PhotoTag name during transition?
Are there any existing logos or customer quotes we can use immediately?

Document created for website planning purposes.

3.7 KiB Raw Blame History Unescape Escape