Publishes working routes
The catalog points visitors to systems they can open and use, not static sales mockups. A working route lets an evaluator judge current behavior before beginning a conversation.
About Intent Demos
Intent Demos is a public inspection catalog that shows working demos, evidence trails, dated measurements, and source for buyers and practitioners who want to inspect behavior before they hire or adopt.
Each entry must open something real or resolve to an attributable public record. The catalog labels team systems and founder contributions separately.
What Intent Demos does
Connects claims to evidence
Entries pair the artifact with source, adoption signals, or an attributable public record when those exist. That connection makes the proof inspectable and exposes the boundary when source is private.
Dates measurements
Time-sensitive counts carry a source and an as-of date. Visitors can separate a current measurement from an evergreen capability claim.
Maps the Intent Solutions network
The catalog connects systems to the sibling property that owns the next job, including Learn, Omarchy, and Tons of Skills. Visitors can inspect here, then move to education, installation, or an outcome conversation with context intact.
What makes Intent Demos different
19 catalog routes are checked
The current repository gate expects 19 primary routes and fails when the catalog count drifts. Each primary card must open a deployed artifact or public record.
Proof has provenance
Public metrics link to their sources and screenshots keep provenance sidecars. The catalog states when a number reflects interest, adoption, or contribution rather than customers.
Attribution stays precise
Founder contributions to outside repositories are labeled separately from Intent Solutions team systems. A merged pull request is evidence of accepted work, not a claim of employment, partnership, or client status.
Failures and limits remain visible
Public artifacts are presented with their current status and evidence boundary. Retired experiments and unsupported relationship claims do not become flagship proof.
The artifact leads
The primary action opens the system, repository, or measurement instead of another layer of promises. Visitors can decide from behavior before they contact the team.
Who uses Intent Demos
- Buyers evaluating an AI implementation partner through working behavior and public evidence.
- Operators who need to see ownership, measurements, and failure boundaries before adoption.
- Technical founders comparing production-shaped systems with pitch-deck concepts.
- Engineers and practitioners looking for source, implementation patterns, and attributable upstream work.
The team behind Intent Demos
Jeremy Longshore, founder
Jeremy Longshore founded Intent Solutions in Gulf Shores, Alabama, after building production AI systems and tools in the Claude Code ecosystem. He contributes systems and public upstream work while keeping those contribution records separate from company delivery claims.
The Intent Solutions team
Demos is founder-led and team-built, with systems attributed at the artifact level. The public roster for this property is [[PUBLIC_TEAM_ROSTER]].
How Demos started
The catalog grew from a set of working demo routes that needed a single public inspection layer. Intent Solutions organized them around receipts, dated proof, and honest attribution so evaluators could judge the work directly.
How Intent Demos works
Choose a system
Start with the job, product, or evidence type closest to the outcome you are evaluating.
Open the artifact
Run the public route or inspect the linked source and current product surface.
Follow the receipt
Check the date, source, measurement, and stated limitation behind the claim.
Bring an outcome
Use the site contact form to describe what must work and how success will be judged. The team's response and project turnaround targets are [[RESPONSE_AND_TURNAROUND_TARGET]].
Key facts
| Company Name | Intent Demos |
|---|---|
| Type | Public inspection catalog of working systems |
| Founded | [[FOUNDING_YEAR]] |
| Founder | Jeremy Longshore |
| Headquarters | Gulf Shores, Alabama |
| Website | demos.intentsolutions.io |
| Core Offering | 19 checked catalog routes with working artifacts and evidence links |
| Pricing | Free public inspection; project pricing [[PROJECT_PRICING_MODEL]] |
| Contract Terms | [[CONTRACT_TERMS]] |
| Services | Working demos, source links, dated measurements, public proof, and outcome intake |
| Communication | Site contact form and jeremy@intentsolutions.io |
| Notable Clients | [[PUBLICLY_NAMED_CLIENTS]] |
| Customers Served | [[VERIFIED_CUSTOMERS_SERVED]] |
| Projects Delivered | 19 public catalog routes in the current checked inventory |
| Competitors | [[NAMED_ALTERNATIVES]] |
| Social | Intent Solutions on GitHub |
| Part of | Intent Solutions, with Learn, Omarchy, and Tons of Skills |
Frequently asked questions
What is Intent Demos, exactly?
Intent Demos is the public inspection catalog for working Intent Solutions systems. It connects each claim to a runnable route, source, dated measurement, or clearly labeled evidence boundary.
Who is Intent Demos for?
It is for buyers, operators, technical evaluators, and practitioners who want to inspect behavior before adopting or hiring. It is not a gallery of pitch-deck mockups.
How is this different from a portfolio site?
The catalog requires a working route or attributable public record behind every primary entry. Metrics include sources, dates, and limitations instead of standing alone as marketing claims.
How do I start?
Open a relevant system, follow its proof links, and judge the behavior directly. Use the contact form when the evidence matches an outcome your team needs.
What does engagement cost?
Intent Demos is free to inspect. Project pricing and contract terms are determined by Intent Solutions for the requested outcome.
How does Demos relate to Intent Solutions?
Demos is the public inspection layer in the Intent Solutions network. The parent practice frames and operates systems while sibling properties publish education, plugins, and reusable agent skills.
Where is the evidence?
Each catalog entry opens a working route or public record. The home proof board also publishes dated measurements, source links, and explicit attribution boundaries.
Start with the behavior. Open the catalog and inspect the system that matches your outcome.
Inspect the systems