Products as evolving systems, not case-study trophies. Each cluster holds the product, its architecture, the agents that work on it, the automation around it, the commercial model, and the questions still open.
Most local search is built around premises: a pin on a map, an address, opening hours. That works for shops - and fails the mobile professionals who come to you. A plumber, mobile hairdresser or dog groomer with no storefront is nearly invisible in map-based tools, which surface the traditional in-store options instead. FoundMyPro exists to give these come-to-you professionals a place of relevance online: structured provider and service data organised around where they work rather than where they sit, strong local search, and an affiliate model that earns from connections rather than charging providers before the platform has proven its value.
Conventional discovery tools assume a business has premises. Mobile professionals who travel to the customer often have no address to anchor a map listing, so searches return in-store options while the come-to-you providers stay invisible.
Search-first UX: structured service taxonomies, location-aware queries, and pages designed to answer the question a searcher actually typed.
The real asset. Structured, verified provider and service data - most engineering effort goes into acquisition, normalisation and freshness.
Programmatic local pages built for genuine usefulness first, rankings second. Search authority is the growth engine, so quality thresholds are strict.
Revenue from connecting demand to providers via affiliate partnerships - chosen over subscriptions to keep incentives aligned with users while the platform earns trust.
Data pipelines, page generation, freshness checks and rank monitoring are automated; agents assist with content quality review under human sampling.
Boring, reliable infrastructure. Every architectural choice is weighed against being one person operating a real platform.
Ambition versus resources versus speed, decided weekly. The platform grows by compounding data quality, not by feature count.
How far affiliate revenue scales before provider-side products make sense. Whether programmatic local pages hold rankings as search itself becomes answer-driven.
Operating a real platform disciplines ambition: every feature competes with data quality work, and data quality usually wins. Speed came from cutting scope, not adding agents.
A mobile companion for software teams that need a clear view of production when they are away from a desk. It turns selected Sentry events into focused alerts, brings the evidence needed for a first assessment onto the phone, and supports deliberate triage without trying to replace Sentry or a paging platform.
Production issues do not wait for an engineer to be at a desk. The normal Sentry workflow is desk-centred, while mobile notifications alone rarely provide enough context to make a sound decision. Sentinel is intended to close that gap between awareness and informed triage.
Selected Sentry events become push alerts. From the app, an engineer can see whether a workspace is calm or needs attention, inspect issue details, stack traces, tags and activity signals, then resolve, archive, snooze or continue in Sentry. The human remains in control.
Sentinel sits beside a production monitoring workflow, where duplicate alerts, stale state or false confidence can be harmful. Its design treats notifications as hints and Sentry as authoritative, minimises data sent to devices, suppresses duplicates, retries carefully and degrades towards silence and reconciliation when certainty is lost.
Connecting a workspace can involve Sentry credentials, device identifiers and customer-controlled issue data. That creates serious security, privacy, support and contractual responsibilities. Sentinel is therefore positioned as a best-effort companion for awareness and triage, not a guaranteed pager, primary monitor or autonomous incident-response system.
The main launch blocker is not a missing feature. It is personal liability. I am not prepared to accept customers while a missed notification, security failure or data incident could expose me directly. Launch requires an appropriate legal entity, suitable insurance and legally reviewed protections before that risk is responsible to take.
No invented metrics, customers or revenue appear on this page. Numbers arrive when they exist.