I build systems that survive the person running them.

Built an occupancy tracking system for the Taqwa Studios office: a smart-lock webhook plus CCTV snapshots run through face recognition, logging who enters and when. The backend flags breaches (out-of-hours access, exceeding allocated slots) and surfaces peak and quiet hours and per-person usage for admin review. Busy and quiet periods are read from two combined signals, live headcount and ambient sound level, rather than headcount alone, giving a more accurate picture of when the space is in active use versus just occupied.

Built a content operations platform: AI generates on-brand carousels, reels, scripts and posts, schedules them, and auto-publishes to Instagram and Threads with analytics synced back, plus a Meta ad campaign builder (campaigns, ad sets, creatives) end to end without leaving the tool. One calendar runs every brand and channel from a single workspace, from raw idea to published post.

Built an end-to-end prospecting tool for Vision Reality: sources leads and pulls Companies House, Google Maps and Google Search data to build a full research profile on each one. From that research it generates a cold email and cold-calling strategy unique to that specific lead, matched against my company playbook. It can also group leads into segments and send the emails directly through an Instantly integration instead of handing off to a separate tool.

Built a structured "second brain" that runs my ventures: an Obsidian vault paired with an AI-agnostic layer, governed by a single file the assistant reads at the start of every session. It defines what to load, which of four operating personas a task needs (Productivity, Content, Growth, Builder), and where every new file belongs. Knowledge (Islamic knowledge base, meeting notes, ideas), live operations (pipelines, finance, trackers), and memory (dated session logs of what happened, decisions, blockers, next steps) are kept in separate, purpose-built folders so the assistant never confuses what I know with what I did. It also encodes a lead-pipeline protocol wired to a Notion CRM, a content protocol (voice guide, platform-specific style files, an anti-AI-writing checklist), and file-naming and routing rules enforced on every save. Runs as the shared knowledge and operations layer across all of my ventures.

Built an offline time-tracking app to see exactly where my hours go across ventures (Vision Reality, Taqwa Studios, Solah Systems and more) and activity types (sales, marketing, client work, admin). Multiple concurrent timers with pause and resume, manual entry, and billable £ tracking, feeding an analytics dashboard that breaks down hours and billable value by venture, activity and period. Used it to catch where I was spending time without matching output and rebalance. Runs entirely offline, no subscription, no cloud dependency: data stored locally and version-controlled with git.