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.
Many development companies keep their team behind a contact form. We publish ours because accountability needs a name attached. Every person on this page appears in the company's public organization records, and each one is the point of escalation for the function they run.
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.
- Stays directly involved in key client relationships and larger programs.
Usama Asif founded Timeline Digital in 2013 and holds two roles that most companies split between two people. As chief executive he is responsible for the company's direction and for the commercial commitments made to clients. As chief technology officer he is responsible for how software actually gets built.
On the technology side, he sets the architecture standards that projects follow: how systems are structured, which technologies the teams standardize on, and what the security and review baseline looks like before any code reaches a client. When a project needs a pattern the company has not used before, that decision passes through him rather than being made quietly inside one team.
On the client side, he remains involved in key relationships. On larger engagements, clients deal with him directly at scoping, at major architecture decisions and at milestones. The practical value of the dual role is simple: the person who makes the commercial promise is the same person accountable for whether the engineering organization can keep it.
The company he founded in 2013 has grown into an organization of 1,200+ developers, direct and group-company employees. His role has changed with that growth, from building systems himself to setting the standards other people build by, but the technology mandate has never moved to a separate department. Engineering standards at Timeline Digital are still owned at the top of the company, not delegated out of sight.
To be clear about the limits, he does not write code on every project or sit in every stand-up. The leads below own their functions day to day. His time concentrates where risk concentrates: 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. These are the same people listed in the company's public organization records, not placeholder profiles.
Fatima Mobeen
VP of Engineering
Owns engineering standards across Timeline Digital's development teams. Her remit covers code quality baselines, technical review policy and the engineering side of hiring, so the way one team builds matches the way every other team builds. Architecture decisions agreed at project start pass through her function on the way to delivery.
Saif Ali
Head of Development
Runs the day-to-day of software delivery: sprint planning, team lead assignments and the allocation of developers to client projects. When a project needs more hands or a different skill mix, that call sits with him. He is the first management contact for delivery questions on active builds.
Ayesha Tariq
Lead UI/UX Designer
Leads the design practice, from early user flows and wireframes through to the finished interfaces clients approve. Her team owns design review across projects, so the screens that ship stay consistent, accessible and usable rather than depending on the taste of whoever happened to build them.
Ahmed Hassan
Cloud Infrastructure Lead
Responsible for the environments client systems run on: cloud and on-premise hosting decisions, deployment pipelines, monitoring, backups and the security posture of production infrastructure. His function is accountable for systems staying up after launch, not just working at handover.
Hamza Raza
Head of Quality Assurance
Heads the quality assurance function that plans testing, runs manual and automated test cycles and signs off release readiness. QA engineers report through him rather than through development leads, so the people testing a build do not answer to the people who wrote it.
Bilwal Khan
Management Head
Runs client operations: contracts, scheduling, resourcing across the management group and the commercial side of active engagements. He is the standard escalation point when a client wants a management-level answer to a question that is not a technical one.
Sidra Noor
Marketing Head
Leads marketing and public communication, including how Timeline Digital describes its own work on this site. Her remit includes keeping published claims aligned with the company's maintained facts rather than letting marketing copy drift ahead of what the delivery teams can actually stand behind.
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+
Active clients 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 costs 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.
| Decision | Owned by | What the client sees |
|---|---|---|
| Scope and commercial terms | Bilwal Khan, with Usama Asif on larger engagements | A written scope the client reviews and signs before any build work begins |
| 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 costs and 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: a written scope before work begins, a staging environment clients can review as the system grows, 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 what it is like to work inside it.
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 verified facts behind every figure used on this site.
Read about the companyCareers at Timeline Digital
What it is like to work under this management group: the roles the company hires for, how engineers grow into team leads, and why the review structure described on this page applies to internal work just as much as client work.
See open rolesWant to talk to the people on this page rather than read about them? Scoping conversations involve the relevant function leads from the first call.
Discuss your software requirements with Timeline DigitalTell us your problem. Get a clear plan and price.
Describe what is slowing your business down. On a free call we will tell you what to build, how long it takes and what it costs.
- A senior specialist joins the conversation
- NDA available before sensitive details are shared
- Written next steps and suitable delivery options