Business discovery
A locally run Python module queries public map data, inserts new lead records, and skips matching name-and-address conflicts. Records without an address may still duplicate.
Linfy Beacon
Local prototypeLinfy Beacon is a locally developed prototype with separate modules for public business discovery, website assessment, and AI-assisted outreach drafting. Integrated orchestration remains planned.
Have a question before starting? Message us directly on WhatsApp.
The problem
A business without a current website or clear online presence can be difficult for a prospective customer to find. Identifying that gap manually across local areas is slow, inconsistent, and difficult to track responsibly.
Beacon was designed as a practical exploration of how public business data, website signals, structured records, and careful drafting could support a more focused local outreach workflow.
Discovery, with context
The local discovery module collects public business information for separately invoked assessment and outreach modules.
A locally run Python module queries public map data, inserts new lead records, and skips matching name-and-address conflicts. Records without an address may still duplicate.
A separate assessment module generates notes from available website data or a missing website URL in the source record.
A drafting module uses a stored template and an AI-assisted rewrite of assessment notes to prepare an email draft.
A local sender module attempts to log sends on a best-effort basis. A send may succeed even if its log entry fails.
Assessment, not assumption
The assessment process generates notes from available website data or a missing website URL in the source record. A missing URL does not prove that a business has no website, and automated findings need verification before they are used in outreach.
The prototype does not enforce human review. Review is recommended before outreach, alongside appropriate production safeguards.
The workflow
Discovery, assessment, drafting, and sending exist as separate local modules. Integrated orchestration and event handling remain planned; send logging is best-effort and can fail even when a send succeeds.
AI-assisted drafting
Beacon uses a stored template and prompts an AI model to rewrite assessment notes for an outreach draft. Notes can contain multiple findings, and the generated rewrite is not automatically validated.
Technology stack
The prototype uses services chosen for separate local modules. The stack below describes the local implementation, not a public SaaS platform.
Local discovery, assessment, drafting, and sender modules.
Lead state, templates, and outreach-log data model.
Public business discovery by category and mapped area.
Website-content extraction used by the assessment module.
Prompted rewrite of assessment notes for an email draft.
A local email delivery integration module.
Development journey
Beacon is being developed as a careful local prototype. The next work is about validation, operating controls, and evidence rather than presenting unfinished automation as complete.
A local data model and separate discovery, assessment, drafting, and sender modules establish the prototype's components.
Review assessment quality and complete controlled sender verification. Outreach logging is best-effort rather than guaranteed.
Add integrated orchestration, scheduling, stronger send safeguards, unsubscribe handling, and event processing before representing those capabilities as active.
Start with the workflow
An Automation Audit is Linfy's current starting point for understanding one workflow before deciding whether a technical next step is appropriate.