Sanitized client deliveryBusiness Directory Automation
A scraping, enrichment, deduplication, and Google Sheets pipeline for a 149,000-member UK business directory.
System routeRead left to right
- 01Directory
- 02Extract
- 03Enrich
- 04Dedupe
- 05Sheet
01 / Context and problemThe operational problem
The client needed useful, structured business records from a large directory without manually collecting, cleaning, and reconciling entries.
OwnershipOwned discovery, pipeline design, data extraction, normalization, enrichment, duplicate handling, delivery structure, and client handover.
02 / Technical challengeWhat made it non-trivial
Large directories contain inconsistent fields and duplicates. Delivery had to remain reviewable by a nontechnical team.
Client identity is confidential.
Targets, selectors, enrichment vendors, and record samples are withheld.
No unverified throughput or accuracy figure is claimed.
03 / System designThe architecture decision
The workflow separated collection, normalization, enrichment, identity matching, and spreadsheet sync so each stage could be inspected and rerun independently.
01Python02Web scraping03Data enrichment04Deduplication05Google Sheets
04 / ReliabilityDesigned for the failure path
- 01
Stage-separated processing
- 02
Duplicate detection before delivery
- 03
Structured review output
- 04
Private selectors and target-specific logic withheld
05 / Result and evidenceWhat this system proves
The delivered system produced a usable business-data pipeline and led to a joint-venture proposal, as recorded in the supplied resume.
Tayyab can translate difficult web data into a client-operable business workflow.
06 / LessonsWhat carries forward
01A clean delivery schema matters as much as collection.
02Enrichment should remain separate from source-of-truth fields.
03Sanitized architecture can still show engineering ownership.