Leadership and Management
Timeline Digital is run by a named leadership group, not an anonymous org chart. This page lists the people who set direction and answer for client work: the founder who still holds the CTO role, and the leads who own engineering, delivery, design, cloud infrastructure, quality assurance, client operations and marketing week to week.
We publish names and roles because accountability needs a name attached. Each person on this page is the point of escalation for the function they run. Timeline Digital has 1,200+ developers and 85+ management professionals, including group-company employees; the full company facts are on the about page.
Who founded Timeline Digital?
One person holds both the commercial and the technical mandate, which shapes how the whole company behaves.
Usama Asif
CEO and CTO
- Founded the company in 2013 and has led it since.
- Sets the architecture and engineering standards used across projects.
Usama Asif founded Timeline Digital in 2013 and holds two roles that many companies split between two people. As chief executive he is responsible for the company's direction and for the commitments made to clients. As chief technology officer he is responsible for how software is built, including the architecture and engineering standards projects follow.
The leads below own their functions day to day. His involvement scales with project size and risk: new architecture, larger programs and anything a client has escalated.
Who runs each function at Timeline Digital?
Each lead owns a defined span of the company's work and is the named point of accountability for it. Names and roles only: we do not publish biographies each person has not reviewed.
Fatima Mobeen
VP of Engineering
Leads engineering standards across the development teams: code quality baselines, technical review policy and the engineering side of hiring.
Saif Ali
Head of Development
Runs day-to-day software delivery: sprint planning, team lead assignments and the allocation of developers to client projects.
Ayesha Tariq
Lead UI/UX Designer
Leads the design practice, from user flows and wireframes to the interfaces clients approve, including design review across projects.
Ahmed Hassan
Cloud Infrastructure Lead
Responsible for hosting decisions, deployment pipelines, monitoring, backups and the security of production infrastructure.
Hamza Raza
Head of Quality Assurance
Heads quality assurance: test planning, manual and automated test cycles, and release sign-off, independent of the development leads.
Bilwal Khan
Management Head
Runs client operations: contracts, scheduling, resourcing across the management group and the commercial side of active engagements.
Sidra Noor
Marketing Head
Leads marketing and public communication, including keeping what this site says in line with the company's maintained facts.
These are working roles, not titles on a slide. During an engagement you meet the leads whose functions your project touches: design approvals come through Ayesha Tariq's practice, staffing decisions through Saif Ali, release sign-off through Hamza Raza's function, and anything commercial through Bilwal Khan. If a question sits between two functions, the leads resolve it between themselves rather than passing the client back and forth.
What does this team run day to day?
The figures below come from the company's maintained facts file, the single source used across this site, reviewed by leadership rather than written by marketing.
85+
Management and service professionals in the group this team leads
1,200+
Developers, direct and group-company employees
1,500+
Projects delivered since 2013
860+
Clients served across 25+ countries
The leads named on this page sit at the top of a wider management group of 85+ professionals. That group is the layer clients actually work with every week, and it covers six kinds of work.
Project management
Delivery owners who run the sprint cycle, keep the plan honest and act as the client's day-to-day contact.
Business analysis
Analysts who turn requirements conversations into written specifications both sides can hold each other to.
Quality assurance
Test engineers who plan and run manual and automated testing under the QA function, independent of the build teams.
Security review
Staff who check access control, data handling and the security baseline on builds before they reach production.
Implementation and support
The people who handle deployment, training and handover, then stay on for maintenance after launch.
Design and infrastructure
The designers and infrastructure engineers who staff the functions Ayesha Tariq and Ahmed Hassan lead.
The leadership team's job is to keep that layer consistent, staffed and accountable, so a client's experience does not depend on which project manager they happened to get.
How does leadership stay close to delivery?
A management layer only helps clients if it actually touches the work. Four mechanisms keep this group connected to projects instead of sitting above them.
Defined spans of responsibility
Each lead owns one function, with team leads reporting into them, sized so that review is real rather than nominal. With 1,200+ developers as direct and group-company employees, no single person reads every line of code, and we will not pretend one does. The structure exists so that someone accountable reviews every project, and so it is always clear who that person is.
Fixed review checkpoints
Projects pass named checkpoints: scope sign-off before work begins, architecture review before the build starts, design review before implementation and quality assurance sign-off before release. Each checkpoint is owned by one of the leads on this page, not by the project team grading its own work, which is what keeps the checkpoints honest.
A written escalation path
Every engagement has a named delivery owner. If something is going wrong, clients escalate to the relevant function head, from there to Bilwal Khan as Management Head, and on larger engagements to Usama Asif directly. The path is part of how engagements are set up at the start, not something improvised after a problem appears.
Honest about the limits
Leadership involvement scales with project size and risk. A small website build is not personally reviewed by the CTO, and it would be dishonest to suggest otherwise. Larger programs get direct leadership attendance at scoping, architecture decisions and major milestones, because that is where a wrong decision hurts a client the most.
Who owns which decision on a client project?
Accountability is only useful if a client can point at it. The table below maps the decisions that shape a project to the person who owns them, and to what the client sees at each point.
Swipe to see the full table →
| Decision | Owned by | What the client sees |
|---|---|---|
| Scope and commercial terms | Bilwal Khan, with Usama Asif on larger engagements | A written plan the client reviews, a free pilot, then the full build with clear change approval |
| System architecture | Usama Asif, with Fatima Mobeen | The chosen approach explained in plain language at the architecture review, with the trade-offs on the table |
| Team composition and staffing | Saif Ali | A named team shared at kickoff; staffing changes are communicated, never silent |
| Interface and experience design | Ayesha Tariq | Designs approved by the client before implementation starts, not after |
| Hosting and infrastructure | Ahmed Hassan | Cloud and on-premise options presented with their trade-offs; the client makes the call |
| Release readiness | Hamza Raza | QA sign-off and release notes shared before anything goes live |
None of this replaces the basics: an approved plan before development begins, a free pilot clients can test before the full build, and delivery in short cycles so problems surface early. Those practices are described in full on the process page. The leadership structure exists to make sure they happen on every project, not only on the ones someone senior happens to be watching.
Where does this team fit in the wider company?
Leadership is one slice of the picture. The pages below cover the company itself and how it delivers.
About Timeline Digital
The full company story: founded in 2013, headquartered in Islamabad, and built into an organization of 1,200+ developers serving clients in 25+ countries. The about page also carries the company facts block behind every figure used on this site.
Read about the companyHow this team delivers
The five steps this leadership group enforces on every project: Understand, Plan, Select Technology, Pilot, and Build & Scale. Clients test our work on a few important modules before committing to the full build.
See our processWant to talk to the people on this page rather than read about them? Tell us about your project and we will involve the leads whose functions it touches.
Discuss Your ProjectStart a conversation
Tell us how your business works.
Describe what is slowing your team down. We will help you work out what to build, and how a free pilot lets you judge our work before the full project.
Prefer WhatsApp? Start a chatWhat happens next
You send a short brief
The problem, the people involved and any target date. A senior engineer replies within 4 business hours.
We understand your workflow
A first call about how your business works today. An NDA can be signed before you share details.
You test a free pilot
You choose 2 to 3 key modules and we build them first, so you judge real software before the full project.