A pipeline that keeps moving.
Turn scattered prospect information into structured CRM records and a clear follow-up queue.
I'm Abdullah. I bring commercial experience and hands-on automation together to connect the work between your inbox, CRM and operations.
Based in Pakistan · Open to remote opportunities
Three business scenarios that connect my commercial background with the workflows I focus on building.
Turn scattered prospect information into structured CRM records and a clear follow-up queue.
Separate routine product and delivery questions from issues that need a person to step in.
Capture buyer requirements, commercial signals and next steps without rebuilding call notes by hand.
These are illustrative system designs grounded in my business experience, not claims of production deployments at these companies. Demos use synthetic data. Client-specific implementation details and outcomes are available only where permitted and verified.
Explore the inputs, decisions and outputs of four automation patterns. Browser-based simulations, no accounts or live integrations required.
Deterministic demonstration logic, not an LLM API. Nothing is sent, scheduled or written to a CRM. Avoid entering confidential information.
Run a simulated dubbing job for a product launch. Repair timing, resolve voice consent or replay a failed render. Each language clears its own release gate.
Portfolio prototype using sample translations, simulated audio timings and mock renders. Caption and manifest exports are generated locally.
When a company submits its registration details, ComplyOne starts a Sumsub business check automatically. If the workspace requires a second check, it also routes the case to VOVE ID. A possible screening match puts onboarding on hold and gives the workspace owner one case to review.
This portfolio prototype uses fictional company data and simulated API responses and alerts. A live integration would call providers from the backend, authenticate provider callbacks and restrict case evidence to authorized reviewers. Sumsub API · VOVE ID KYB
Executable browser examples and implementation blueprints: explicit contracts, controlled side effects and observable failures.
Run a small event processor with a duplicate event, an API failure or an unapproved action. The state machine below runs locally in JavaScript.
Awaiting event...
Retries are simulated immediately. Production requires durable storage, a queue and atomic uniqueness constraints.
A CRM extraction should distinguish missing information from facts, with a trace back to the source.
{
"schema_version": "1.0",
"event_id": "call_demo_001",
"company_id": "demo_company",
"requirements": [{
"value": "Multilingual speech analytics",
"evidence": "We need multilingual speech analytics",
"source": "transcript:turn_1"
}],
"budget": null,
"timeline": null,
"next_action": "schedule_technical_review",
"write_status": "pending_approval"
}Validate types and allowed values before proposing a write. A model-generated confidence score alone should never authorize a CRM update.
Separate product and policy retrieval from order access. A product question can use approved public content. Order details require a verified customer and order match.
request → classify → permission check product route: approved product index order route: verified order lookup sources → grounded draft → policy check → review
Proposed architecture. No vector database or private order data is connected to this portfolio.
Run a deterministic policy regression suite. These checks exercise routing rules; they do not measure an LLM's quality.
Ready to evaluate: opt-out, closed deals, missing identity, missing approval, valid next action and invalid timing.
For a real model pipeline: add labeled fixtures, field-level precision and recall, unsupported-claim checks, prompt-injection cases, latency and cost budgets.
These engineering examples were built for this portfolio. Architecture proposals and sample schemas are not production deployment claims.
External GitHub projects relevant to the designs above. Linked as references, with credit to their maintainers.
A fair-code workflow automation platform. Relevant to webhook ingestion, API integrations and review handoffs in the Marlead example.
n8n-io/n8n ↗Tools for evaluating and red-teaming LLM applications. Relevant to regression tests for extraction and grounded customer replies.
promptfoo/promptfoo ↗PII detection and anonymization tooling. A reference for reducing personal data in messages and transcripts before model processing.
data-privacy-stack/presidio ↗Third-party repositories. No authorship, contribution, affiliation or prior implementation is implied. Review each project's license and deployment requirements before use.
Define the trigger, source of truth, owner and what a successful outcome looks like.
Use APIs, validated fields and explicit routing. Give ambiguous requests a human review path.
Design for retries, duplicate events, missing data, approval boundaries and a useful audit trail.
My experience spans commercial leadership at Qorden AI, GTM advisory through Marlead and running Feliz Pakistan. That means seeing the work from the sales team, the operator and the customer's side.
I focus on the handoffs: where a conversation becomes a task, a task becomes a follow-up, and a follow-up either moves the business forward or gets lost.
Architecture options shown for these demos. Specific tool experience and production references can be discussed directly.
Let's start with one workflow and a clear outcome.
abdullahismail100@gmail.com