/fyd
Give FYD your business.
It keeps your whole digital presence.
FYD learns your business as connected things: services, locations, projects, people, offers. It builds your website and answers your customers from that understanding. You can see what it knows, ask why it believes it, and correct it in plain words. You stay in control.
Running proof on this server: two demo businesses, built from their FYD understanding.
The 10-second version
This understands my business and keeps my digital presence. Not a website builder: the site is built from the understanding, and the understanding answers my customers.
/understand
FYD understands your business, not your pages
Paste a website address. FYD reads what is public and shows you what it understood: the actual things your business is made of, connected to each other.
A visitor does not experience these as database records. A service is a thing with hours, a price range, and the people who do it. A project is a thing with photos, a location, and the customer it was for. When the business changes, the things change, and every place they appear stays consistent.
Paste-a-URL preview is live below, in the Try it section. No account. Only public information is read.
First 10 seconds
This understands my business and keeps my digital presence.
Next 30 seconds
It knows services, locations, projects, and relationships as real things, not just webpage text.
Next 2 minutes
I can explore those things, ask questions about them, see why FYD believes them, and correct them.
This page is built to pass that comprehension test. If it does not, the page failed, not the reader.
/explore
The margins are the graph
The center stays an excellent, normal business experience. The edges expose real objects. Tap one: it opens, shows its work, and lets you act. Every object proves the same chain, every time. This page is itself an FYD presence: explore the product through the product's own interaction grammar.
Mobile grammar: peek, tap, sheet, related object, ask, why, action, back, exact prior position. Desktop: edge, click, expand, traverse, close.
/see · running proof
Two live demos and PING itself, running on this server
Complete FYD presences generated from their business understanding. Open one, explore its objects, ask it questions, check the why behind its answers.
The two demo businesses are for the product test and are not customer sites. PING Social is the operator's own business, running on the same system.
Demo tenant
Happy Place
A complete business presence generated from its FYD understanding.
Ask about its services, hours, and offers.
Demo tenant
Coppersmith Plumbing
A trades business presence, including conversational customization proven on this demo.
Ask about emergency plumbing and services.
Operator's own business
PING Social
PING's own business running on the same system: the operator's real presence, built from its FYD understanding.
Ask about AI call answering, lead follow-up, scheduling support, and admin automation.
/how
How it works: the loop
Information enters as public observation and moves through a loop that makes it increasingly useful. Every cycle produces new evidence, which feeds the next cycle.
Observe
FYD reads your public sources.
Your website, listings, and anything else public about the business. Only public information is ever read at this step.
Understand
Builds a model of your business as connected things.
Services, locations, people, offers, projects, and how they relate. Not page text: actual things.
Build
Generates your presence from that model.
Your website and customer-facing answers come from the understanding, so they stay consistent with each other.
Keep current
Re-reads sources and folds in changes. Your corrections survive.
When the business changes, the understanding updates and every place it appears follows. Owner corrections persist across rebuilds.
Help
Ask FYD answers customers from evidence.
Answers cite their sources. When the evidence is missing, FYD says it does not know instead of guessing.
Act with permission
Routine work happens only when you approve it.
FYD can propose work, but nothing acts on its own. Each step waits for your explicit approval.
Learn
Outcomes become new evidence.
What worked and what did not feeds back into the understanding, so the system gets more useful instead of resetting.
Learn → Observe
The loop closes
New evidence feeds the next cycle.
Observe, understand, build, keep current, help, act with permission, learn. Then observe again, with a better understanding than before.
/ask
Ask FYD. It answers from evidence, or says it does not know.
Ask about the Coppersmith Plumbing demo below. Every answer comes from that business's recorded evidence. No evidence, no answer: FYD says so honestly instead of guessing.
Visitor mode: public objects only. Try a question with no answer in the record, like the owner's favorite color, and watch the honest refusal. That refusal is the feature.
Answers cite sources
Every answer carries the evidence it came from.
No evidence, no answer
Missing evidence produces an honest refusal, never a guess.
Fail closed
If the service cannot answer, it says so. It never invents.
/why
Why this? Every claim shows its work.
Tap it on any claim. FYD walks you back through the record: the value, the object field, the claim, the evidence, the observation, the source.
Coppersmith Plumbing offers emergency plumbing.
Why this?
Coppersmith Plumbing offers emergency plumbing.
- What you see:Emergency plumbing, listed under services
- Object field:service.offered
- Claim:read from the business's public website
- Evidence:page text, fetched and recorded 2026-09-24
- Source:the business's public website
Illustrative lineage. On a live demo site, this lineage is computed from the actual evidence record behind the claim.
/correct
Correct FYD in plain words
FYD will get things wrong. That is expected. What matters is what happens next: you say it plainly, you approve the fix, and it stays fixed.
01
You say it in plain words
On the Coppersmith demo, the owner typed: "Move emergency plumbing first." No settings panel, no ticket, no code.
02
FYD shows the exact change it proposes
Before anything changes, you see precisely what will move, what it affects, and what stays the same.
03
You approve
Nothing changes without your approval. Not the wording, not the order, not the site. Approval is the gate.
04
Your correction survives rebuilds
The next time the presence is regenerated, your correction is still there. You correct FYD once, not every time.
Conversational correction is live on the demo tenants in demo-owner mode, demonstrated on the Coppersmith demo 2026-09-24. Owner authorization is required before any change lands.
/network
Your business in a permission-aware network
FYD is not only a tool for isolated businesses. Presences can connect: businesses, customers, creators, partners, communities. The network grows only from information that is legitimately public or owner-authorized. Never by weakening the boundary.
The boundary rule: live today
Live nowPrivate business data never becomes network data. Only public or owner-authorized information ever leaves your business boundary. Tenant isolation is constitutional, and the network is built from projections, never by weakening it.
Public relationships you choose: coming
ComingYour presence will be able to connect to partners, creators, directories, and community organizations you pick. Each share is explicitly approved by you. A relationship across businesses never implies access to another business's private data.
One identity, many networks: long-term vision
Long-term visionThe design preserves the ability for a FYD presence to reach multiple networks without giving up control of its private data. Open protocols are design direction. They are not built, and no outside service ever becomes the owner of your business identity.
No partner announcements.
FYD names no partners and claims no integrations until there is real evidence and real authorization. When a partnership is real, it will carry the same proof this page demands of everything else.
/inside
PING underneath: the machinery that makes FYD possible
FYD is the human-facing product. PING is the intelligence and orchestration underneath it. You never need to understand PING internals. This is the whole story in nine steps.
The world happens
Live nowA customer calls, a review lands, hours change, a new service launches.
PING notices
Live nowNew information is observed and recorded with its source and time.
PING keeps the record
Live nowThe record is kept durably. Nothing important silently disappears.
FYD shows it to humans
Live nowThe understanding is projected for people: websites, answers, objects you can explore.
People interact and correct
Live nowCustomers ask. Owners correct. Every correction is recorded too.
Boundaries are enforced
Live nowEvery business stays separate. Private data never leaks across.
Approved work gets done
Available with owner authorizationRoutine work you authorized is carried out, step by step.
Results are recorded
Live nowWhat happened becomes part of the record, with its outcome.
The understanding improves
ComingOutcomes become new evidence. The system gets more useful instead of resetting.
FYD makes it human. PING makes it possible. TenantOS makes the boundary safe.
/yours
Your business stays yours
TenantOS is the part of the system that keeps every business separate. FYD runs on that ordinary tenant machinery: no special access, no bypass, no exceptions for the product itself.
Your private data never becomes network data
What is private to your business stays private to your business. The network is built from public or owner-authorized projections only. This rule is live today, not a promise for later.
Nothing is published or shared without your explicit okay
FYD proposes; you approve. Publishing, sharing, and any outward action wait for your explicit authorization, every time.
You can see everything FYD believes, and change it
The understanding is inspectable: what FYD knows, why it believes it, and where it came from. Corrections happen in plain words and survive rebuilds.
The same boundary that protects your data from the network protects the network from your data. One rule, both directions.
/status
What is real
Every capability on this page carries its copy class. Stages, not dates. Product claim never exceeds running proof.
Paste a URL, see what FYD understood
Live nowTwo demo sites generated from their FYD understanding
Live nowAsk FYD answers from evidence, refuses without it
Live nowWHY THIS lineage on visible claims
Live nowOwner proposes changes in plain words, approves them
Live nowCorrections surviving rebuilds
ComingPresence kept current as sources change
ComingRoutine work running on owner approval
Available with owner authorizationOpportunity spotting and proposed work
ComingPublic relationships between FYD presences
ComingOne identity projecting into many networks
Long-term visionNamed partners or integrations
Long-term vision"Named partners or integrations" sits at long-term vision because FYD names no partners until there is evidence and authorization.
FAQ
Questions from business owners
What is PING Social?+
PING Social is the consultancy that applies PING infrastructure to real businesses, starting with home service companies. It helps owners capture more opportunities, reduce administrative work, respond faster, and operate more consistently, with practical AI rather than hype.
How does PING Social work with a business?+
It starts with a conversation about how the business actually runs: where opportunities get missed, where follow-up lags, where admin work piles up. Then PING Social recommends practical automation for those specific problems. Consultative, not one-size-fits-all, and the owner stays in control.
Will AI replace my workers?+
No. That is the opposite of the goal. AI handles repetitive communication, organization, and follow-up so owners and skilled workers can focus on customers, jobs, and decisions that need human judgment. Technology should strengthen the worker, not replace them.
/try
Try it: paste your URL
No account. FYD reads only what is public about the business and shows you what it understood. Value first, registration never before value.
Want the full intake instead? Start a fresh FYD build →