Usama Qamar.
Ship, rank, grow.
I build production software, run full 360° digital marketing, automate the work that compounds with AI + workflow systems, and advise founders as a fractional CTO. One operator, every channel.
Selected work.
All case studies across software, marketing, automation, and founding work, auto-advancing every 2 s. Click any card for the full write-up.
Spring Boot AI Error Analyzer - Open Source Library
The Problem Every Java team I've worked with loses hours per week to the same ritual: an exception fires in production, an engineer copies the stack trace into a chat, scrolls past framework noise to find the one line that matters, then walks back through the
Dubai Property Management - Tenant Lifecycle Automation for 1,800 Units
The Problem A Dubai property manager handling 1,800 residential units across 14 buildings was running its operations the way most mid-sized PM companies do. heroically, on the goodwill of overworked staff. Tenant onboarding took 4-7 days. Maintenance requests
London Boutique Law Firm - Contract Review and Intake Automation
The Problem A 9-lawyer commercial firm in central London was watching its margins erode under the weight of non-billable work. Lawyers were spending 8-12 hours a week each on tasks that didn't bill: reviewing routine NDAs, summarising lengthy contracts for par
Karachi Cardiology Clinic - From Manual Front Desk to Self-Running Intake
The Problem A single-consultant cardiology clinic in Karachi was running everything through one front-desk attendant: phone bookings, WhatsApp enquiries, appointment reminders, follow-up calls, lab report distribution, and ad-hoc patient questions. The consult
Austin B2B SaaS - Customer Onboarding and Support Triage Automation
The Problem A 32-person B2B SaaS company had recently raised a Series A and was acquiring customers faster than its 4-person customer success team could onboard them. New customers were waiting 2-3 weeks for a kickoff call. Support tickets were piling up in Li
Riyadh E-commerce - Arabic-First Customer Service and Multi-Channel Listing
The Problem A Saudi DTC home goods brand was selling on Salla, Amazon.sa, Noon, and Instagram. Customer service was running through a 6-person team handling Arabic and English in roughly equal mix; response times averaged 3 hours during the day and 14 hours ov
Lahore Couriers - AI Dispatch and Customer Comms for a 60-Rider Fleet
The Problem A 60-rider last-mile courier company in Lahore was assigning deliveries by spreadsheet. every morning, two dispatchers sat with the day's orders and manually grouped them into rider routes. Customer notifications were sent by hand from a single SIM
Islamabad Real Estate Developer - Sales Pipeline Automation at Scale
The Problem A 380-person developer with multiple active projects was leaking leads at every stage of the funnel. Inbound enquiries arrived across 7 different channels (website, Meta ads, IG DMs, WhatsApp, walk-ins, agent referrals, phone). Each channel had its
Manchester Manufacturer - Invoice OCR and Vendor Management at Scale
The Problem A 1,200-staff engineering manufacturer in the Manchester area was processing 14,000+ vendor invoices per month through a 9-person AP team. Each invoice was OCR'd by a legacy system, then manually corrected by humans (the OCR was wrong on roughly 40
Meridian Limo - Local SEM that Filled the Fleet
The Problem Meridian was a well-reviewed limo operator with a clean fleet of 9 vehicles, but inbound demand was unpredictable. Most bookings came from referrals and a thin Google Maps presence. The owner was paying a generalist agency for "SEO + social" with n
NYC Boutique Investment Fund - Pipeline and LP Reporting Automation
The Problem A $180M boutique growth-equity fund with 18 portfolio companies and a 4-person investment team was drowning in process work. Every quarter, the team spent ~3 weeks producing the LP reporting package. emailing portfolio CEOs for KPI updates, chasing
Karachi DTC Cosmetics Brand - Multi-Channel Sync and AI Customer Service
The Problem A founder-led cosmetics brand had grown from one Instagram shop to selling on Shopify, Instagram Shopping, Daraz, and through WhatsApp DMs. across four channels with completely separate inventory tracking. The founder's mother (who managed operatio
Spring Boot AI Error Analyzer - Open Source Library
The Problem Every Java team I've worked with loses hours per week to the same ritual: an exception fires in production, an engineer copies the stack trace into a chat, scrolls past framework noise to find the one line that matters, then walks back through the
Dubai Property Management - Tenant Lifecycle Automation for 1,800 Units
The Problem A Dubai property manager handling 1,800 residential units across 14 buildings was running its operations the way most mid-sized PM companies do. heroically, on the goodwill of overworked staff. Tenant onboarding took 4-7 days. Maintenance requests
London Boutique Law Firm - Contract Review and Intake Automation
The Problem A 9-lawyer commercial firm in central London was watching its margins erode under the weight of non-billable work. Lawyers were spending 8-12 hours a week each on tasks that didn't bill: reviewing routine NDAs, summarising lengthy contracts for par
Karachi Cardiology Clinic - From Manual Front Desk to Self-Running Intake
The Problem A single-consultant cardiology clinic in Karachi was running everything through one front-desk attendant: phone bookings, WhatsApp enquiries, appointment reminders, follow-up calls, lab report distribution, and ad-hoc patient questions. The consult
Austin B2B SaaS - Customer Onboarding and Support Triage Automation
The Problem A 32-person B2B SaaS company had recently raised a Series A and was acquiring customers faster than its 4-person customer success team could onboard them. New customers were waiting 2-3 weeks for a kickoff call. Support tickets were piling up in Li
Riyadh E-commerce - Arabic-First Customer Service and Multi-Channel Listing
The Problem A Saudi DTC home goods brand was selling on Salla, Amazon.sa, Noon, and Instagram. Customer service was running through a 6-person team handling Arabic and English in roughly equal mix; response times averaged 3 hours during the day and 14 hours ov
Lahore Couriers - AI Dispatch and Customer Comms for a 60-Rider Fleet
The Problem A 60-rider last-mile courier company in Lahore was assigning deliveries by spreadsheet. every morning, two dispatchers sat with the day's orders and manually grouped them into rider routes. Customer notifications were sent by hand from a single SIM
Islamabad Real Estate Developer - Sales Pipeline Automation at Scale
The Problem A 380-person developer with multiple active projects was leaking leads at every stage of the funnel. Inbound enquiries arrived across 7 different channels (website, Meta ads, IG DMs, WhatsApp, walk-ins, agent referrals, phone). Each channel had its
Manchester Manufacturer - Invoice OCR and Vendor Management at Scale
The Problem A 1,200-staff engineering manufacturer in the Manchester area was processing 14,000+ vendor invoices per month through a 9-person AP team. Each invoice was OCR'd by a legacy system, then manually corrected by humans (the OCR was wrong on roughly 40
Meridian Limo - Local SEM that Filled the Fleet
The Problem Meridian was a well-reviewed limo operator with a clean fleet of 9 vehicles, but inbound demand was unpredictable. Most bookings came from referrals and a thin Google Maps presence. The owner was paying a generalist agency for "SEO + social" with n
NYC Boutique Investment Fund - Pipeline and LP Reporting Automation
The Problem A $180M boutique growth-equity fund with 18 portfolio companies and a 4-person investment team was drowning in process work. Every quarter, the team spent ~3 weeks producing the LP reporting package. emailing portfolio CEOs for KPI updates, chasing
Karachi DTC Cosmetics Brand - Multi-Channel Sync and AI Customer Service
The Problem A founder-led cosmetics brand had grown from one Instagram shop to selling on Shopify, Instagram Shopping, Daraz, and through WhatsApp DMs. across four channels with completely separate inventory tracking. The founder's mother (who managed operatio
Spring Boot AI Error Analyzer - Open Source Library
The Problem Every Java team I've worked with loses hours per week to the same ritual: an exception fires in production, an engineer copies the stack trace into a chat, scrolls past framework noise to find the one line that matters, then walks back through the
Dubai Property Management - Tenant Lifecycle Automation for 1,800 Units
The Problem A Dubai property manager handling 1,800 residential units across 14 buildings was running its operations the way most mid-sized PM companies do. heroically, on the goodwill of overworked staff. Tenant onboarding took 4-7 days. Maintenance requests
London Boutique Law Firm - Contract Review and Intake Automation
The Problem A 9-lawyer commercial firm in central London was watching its margins erode under the weight of non-billable work. Lawyers were spending 8-12 hours a week each on tasks that didn't bill: reviewing routine NDAs, summarising lengthy contracts for par
Karachi Cardiology Clinic - From Manual Front Desk to Self-Running Intake
The Problem A single-consultant cardiology clinic in Karachi was running everything through one front-desk attendant: phone bookings, WhatsApp enquiries, appointment reminders, follow-up calls, lab report distribution, and ad-hoc patient questions. The consult
Austin B2B SaaS - Customer Onboarding and Support Triage Automation
The Problem A 32-person B2B SaaS company had recently raised a Series A and was acquiring customers faster than its 4-person customer success team could onboard them. New customers were waiting 2-3 weeks for a kickoff call. Support tickets were piling up in Li
Riyadh E-commerce - Arabic-First Customer Service and Multi-Channel Listing
The Problem A Saudi DTC home goods brand was selling on Salla, Amazon.sa, Noon, and Instagram. Customer service was running through a 6-person team handling Arabic and English in roughly equal mix; response times averaged 3 hours during the day and 14 hours ov
Lahore Couriers - AI Dispatch and Customer Comms for a 60-Rider Fleet
The Problem A 60-rider last-mile courier company in Lahore was assigning deliveries by spreadsheet. every morning, two dispatchers sat with the day's orders and manually grouped them into rider routes. Customer notifications were sent by hand from a single SIM
Islamabad Real Estate Developer - Sales Pipeline Automation at Scale
The Problem A 380-person developer with multiple active projects was leaking leads at every stage of the funnel. Inbound enquiries arrived across 7 different channels (website, Meta ads, IG DMs, WhatsApp, walk-ins, agent referrals, phone). Each channel had its
Manchester Manufacturer - Invoice OCR and Vendor Management at Scale
The Problem A 1,200-staff engineering manufacturer in the Manchester area was processing 14,000+ vendor invoices per month through a 9-person AP team. Each invoice was OCR'd by a legacy system, then manually corrected by humans (the OCR was wrong on roughly 40
Meridian Limo - Local SEM that Filled the Fleet
The Problem Meridian was a well-reviewed limo operator with a clean fleet of 9 vehicles, but inbound demand was unpredictable. Most bookings came from referrals and a thin Google Maps presence. The owner was paying a generalist agency for "SEO + social" with n
NYC Boutique Investment Fund - Pipeline and LP Reporting Automation
The Problem A $180M boutique growth-equity fund with 18 portfolio companies and a 4-person investment team was drowning in process work. Every quarter, the team spent ~3 weeks producing the LP reporting package. emailing portfolio CEOs for KPI updates, chasing
Karachi DTC Cosmetics Brand - Multi-Channel Sync and AI Customer Service
The Problem A founder-led cosmetics brand had grown from one Instagram shop to selling on Shopify, Instagram Shopping, Daraz, and through WhatsApp DMs. across four channels with completely separate inventory tracking. The founder's mother (who managed operatio
Latest writing.
Short signal on software, marketing, and the start-up middle, built to be scanned by operators in motion.
When NOT to Use Composer 2.5: 6 Cases Where Opus 4.7 Still Wins
The single most-quoted line in every Composer 2.5 launch piece is that it is "ten times cheaper than the frontier models." That number is accurate at the per-token level. It is also misleading at the per-completed-task level, because a model that needs three a
Composer 2.5 + MCP: The Production Integration Guide (2026)
A pattern from the production audits I have run over the last fortnight: teams switch to Composer 2.5, see the headline 10× cost saving in their per-token bill, and watch the same agent loops still take three or four attempts to land each task. The cost-per-co
RAG vs Long-Context: When Each Actually Wins in Production (2026)
The version of this argument that runs on social media goes like this: long context windows have killed RAG. Claude Opus 4.7 has 1M tokens. Gemini 3.5 Flash has 1M with a Pro that pushes higher. You can just load the documents and ask the question. Vector data
Composer 2.5 vs Gemini 3.5 Flash: When Each Wins on Real Coding Tasks
The first surprise when you sit the two pricing sheets side by side is that the smaller-branded model isn't cheaper. Gemini 3.5 Flash lists at $1.50 per million input tokens and $9.00 per million output. Composer 2.5 lists at $0.50 input and $2.50 output on th
Building a Legal Research Agent: Gemini Flash + Opus 4.7 + RAG (Use-Case Build)
The interesting thing about legal research as an AI use case is that the work is structurally a perfect fit for the tools and yet most of the AI products in the legal vertical do not architect to that fit. The work is high-volume (thousands of pages per case),
The Strangler Fig Pattern: Migrating Legacy Monoliths to Modern Architecture
Most enterprises don't get to build the modern architecture greenfield. They have to migrate into it — from a decade-old monolith, from a sprawling SOA with bespoke point-to-point integrations, from a vendor system that was never designed to be extended the wa
Gemini 3.5 Pro Pre-Read: What June's Release Will Change for Builders
The interesting thing about Gemini 3.5 Pro is what Google did not say at I/O. Flash shipped on May 19th with full benchmarks, pricing, and API availability. Pro got a one-line mention — "coming next month" — and an admission that Google is already using it int
The Transactional Outbox Pattern: Reliable Event Publishing Without 2PC
Every event-driven system depends on a deceptively simple guarantee: when a service commits a state change to its database, the corresponding event must be published. Both happen, or neither does. The system that gets this wrong silently corrupts itself — orde
Claude Code in Production: 9 Months In, What Actually Works (2026)
Claude Code shipped quietly. There was no big launch event, no benchmark theatre — just a CLI that let you point Claude Opus at a codebase and ask it to do things. At the time, the right framing for it was "another agent harness, this one from Anthropic, proba
Service Mesh vs ESB: Where Cross-Cutting Concerns Belong
Service mesh and Enterprise Service Bus solve overlapping concerns. Routing, observability, security, traffic management, retries, circuit breaking — both architectures address all of them. The interesting question is not which is better, because that's a mean
The Saga Pattern: Distributed Transactions Without Two-Phase Commit
Splitting a system into independent services solves a lot of problems. It also creates one specifically nasty new one: how do you change state across multiple services as a single atomic operation, when each service has its own database and there's no shared t
Composer 2.5 Hands-On: What Eleven Real Tasks Actually Revealed
The benchmark numbers on Composer 2.5 are now well-covered ground. I've written about them at length in the original builder's guide, and I've written about the head-to-head comparisons in the vs Opus 4.7 piece. What I hadn't done — and what most of the covera
When NOT to Use Composer 2.5: 6 Cases Where Opus 4.7 Still Wins
The single most-quoted line in every Composer 2.5 launch piece is that it is "ten times cheaper than the frontier models." That number is accurate at the per-token level. It is also misleading at the per-completed-task level, because a model that needs three a
Composer 2.5 + MCP: The Production Integration Guide (2026)
A pattern from the production audits I have run over the last fortnight: teams switch to Composer 2.5, see the headline 10× cost saving in their per-token bill, and watch the same agent loops still take three or four attempts to land each task. The cost-per-co
RAG vs Long-Context: When Each Actually Wins in Production (2026)
The version of this argument that runs on social media goes like this: long context windows have killed RAG. Claude Opus 4.7 has 1M tokens. Gemini 3.5 Flash has 1M with a Pro that pushes higher. You can just load the documents and ask the question. Vector data
Composer 2.5 vs Gemini 3.5 Flash: When Each Wins on Real Coding Tasks
The first surprise when you sit the two pricing sheets side by side is that the smaller-branded model isn't cheaper. Gemini 3.5 Flash lists at $1.50 per million input tokens and $9.00 per million output. Composer 2.5 lists at $0.50 input and $2.50 output on th
Building a Legal Research Agent: Gemini Flash + Opus 4.7 + RAG (Use-Case Build)
The interesting thing about legal research as an AI use case is that the work is structurally a perfect fit for the tools and yet most of the AI products in the legal vertical do not architect to that fit. The work is high-volume (thousands of pages per case),
The Strangler Fig Pattern: Migrating Legacy Monoliths to Modern Architecture
Most enterprises don't get to build the modern architecture greenfield. They have to migrate into it — from a decade-old monolith, from a sprawling SOA with bespoke point-to-point integrations, from a vendor system that was never designed to be extended the wa
Gemini 3.5 Pro Pre-Read: What June's Release Will Change for Builders
The interesting thing about Gemini 3.5 Pro is what Google did not say at I/O. Flash shipped on May 19th with full benchmarks, pricing, and API availability. Pro got a one-line mention — "coming next month" — and an admission that Google is already using it int
The Transactional Outbox Pattern: Reliable Event Publishing Without 2PC
Every event-driven system depends on a deceptively simple guarantee: when a service commits a state change to its database, the corresponding event must be published. Both happen, or neither does. The system that gets this wrong silently corrupts itself — orde
Claude Code in Production: 9 Months In, What Actually Works (2026)
Claude Code shipped quietly. There was no big launch event, no benchmark theatre — just a CLI that let you point Claude Opus at a codebase and ask it to do things. At the time, the right framing for it was "another agent harness, this one from Anthropic, proba
Service Mesh vs ESB: Where Cross-Cutting Concerns Belong
Service mesh and Enterprise Service Bus solve overlapping concerns. Routing, observability, security, traffic management, retries, circuit breaking — both architectures address all of them. The interesting question is not which is better, because that's a mean
The Saga Pattern: Distributed Transactions Without Two-Phase Commit
Splitting a system into independent services solves a lot of problems. It also creates one specifically nasty new one: how do you change state across multiple services as a single atomic operation, when each service has its own database and there's no shared t
Composer 2.5 Hands-On: What Eleven Real Tasks Actually Revealed
The benchmark numbers on Composer 2.5 are now well-covered ground. I've written about them at length in the original builder's guide, and I've written about the head-to-head comparisons in the vs Opus 4.7 piece. What I hadn't done — and what most of the covera
When NOT to Use Composer 2.5: 6 Cases Where Opus 4.7 Still Wins
The single most-quoted line in every Composer 2.5 launch piece is that it is "ten times cheaper than the frontier models." That number is accurate at the per-token level. It is also misleading at the per-completed-task level, because a model that needs three a
Composer 2.5 + MCP: The Production Integration Guide (2026)
A pattern from the production audits I have run over the last fortnight: teams switch to Composer 2.5, see the headline 10× cost saving in their per-token bill, and watch the same agent loops still take three or four attempts to land each task. The cost-per-co
RAG vs Long-Context: When Each Actually Wins in Production (2026)
The version of this argument that runs on social media goes like this: long context windows have killed RAG. Claude Opus 4.7 has 1M tokens. Gemini 3.5 Flash has 1M with a Pro that pushes higher. You can just load the documents and ask the question. Vector data
Composer 2.5 vs Gemini 3.5 Flash: When Each Wins on Real Coding Tasks
The first surprise when you sit the two pricing sheets side by side is that the smaller-branded model isn't cheaper. Gemini 3.5 Flash lists at $1.50 per million input tokens and $9.00 per million output. Composer 2.5 lists at $0.50 input and $2.50 output on th
Building a Legal Research Agent: Gemini Flash + Opus 4.7 + RAG (Use-Case Build)
The interesting thing about legal research as an AI use case is that the work is structurally a perfect fit for the tools and yet most of the AI products in the legal vertical do not architect to that fit. The work is high-volume (thousands of pages per case),
The Strangler Fig Pattern: Migrating Legacy Monoliths to Modern Architecture
Most enterprises don't get to build the modern architecture greenfield. They have to migrate into it — from a decade-old monolith, from a sprawling SOA with bespoke point-to-point integrations, from a vendor system that was never designed to be extended the wa
Gemini 3.5 Pro Pre-Read: What June's Release Will Change for Builders
The interesting thing about Gemini 3.5 Pro is what Google did not say at I/O. Flash shipped on May 19th with full benchmarks, pricing, and API availability. Pro got a one-line mention — "coming next month" — and an admission that Google is already using it int
The Transactional Outbox Pattern: Reliable Event Publishing Without 2PC
Every event-driven system depends on a deceptively simple guarantee: when a service commits a state change to its database, the corresponding event must be published. Both happen, or neither does. The system that gets this wrong silently corrupts itself — orde
Claude Code in Production: 9 Months In, What Actually Works (2026)
Claude Code shipped quietly. There was no big launch event, no benchmark theatre — just a CLI that let you point Claude Opus at a codebase and ask it to do things. At the time, the right framing for it was "another agent harness, this one from Anthropic, proba
Service Mesh vs ESB: Where Cross-Cutting Concerns Belong
Service mesh and Enterprise Service Bus solve overlapping concerns. Routing, observability, security, traffic management, retries, circuit breaking — both architectures address all of them. The interesting question is not which is better, because that's a mean
The Saga Pattern: Distributed Transactions Without Two-Phase Commit
Splitting a system into independent services solves a lot of problems. It also creates one specifically nasty new one: how do you change state across multiple services as a single atomic operation, when each service has its own database and there's no shared t
Composer 2.5 Hands-On: What Eleven Real Tasks Actually Revealed
The benchmark numbers on Composer 2.5 are now well-covered ground. I've written about them at length in the original builder's guide, and I've written about the head-to-head comparisons in the vs Opus 4.7 piece. What I hadn't done — and what most of the covera
The numbers.
What the work adds up to. Updated when the counters move.
Subscribe.
The operator's dispatch.
Software patterns, marketing playbooks, and startup lessons from the field. Written for people who ship, not people who plan to.
OR EMAIL USAMAQAMAR@WEBVIPERS.COM