Leadership
US Life Coaching is led by people who are answerable for what the company builds and how it behaves. Leadership sets company direction, product purpose, and the standard for responsible technology. It also owns customer trust: privacy, evidence, human oversight, and the practical value of USLC’s development systems.
Usman Sana leads the company as Chief Executive Officer. Usman Farooq leads technology as Chief Technology Officer. Together they are responsible for the direction of the company and the integrity of its products.
CEO
Chief Executive Officer
Usman Sana is Chief Executive Officer of US Life Coaching. He is accountable for company direction, the purpose of USLC’s development systems, and the commitments the company makes to the people who use them.
CTO
Chief Technology Officer
Usman Farooq is Chief Technology Officer of US Life Coaching. He is accountable for technology strategy, product engineering, and turning USLC’s human-development concepts into reliable digital products.
CEO
Chief Executive Officer
Usman Sana is Chief Executive Officer of US Life Coaching. He is accountable for company direction, the purpose of USLC’s development systems, and the commitments the company makes to individuals, practitioners, and organisations. He leads USLC as a human-development technology company: behavioural and communication intelligence, lifestyle intelligence, professional development, and leadership and team learning, supported by practitioner-led programmes and human-guided AI. His work is to keep those offers honest. Each system should say what it is for, what a person chooses to share, and where judgement still belongs with the people in the room. He is responsible for organisational leadership, responsible growth, and the governance of public claims. Customer trust sits with him as well—privacy requests, support escalations, and commercial terms are company duties, not something a model can own.
The CEO’s relationship to USLC’s purpose is practical: decide what the company will build, what it will refuse, and how customers should be treated when something goes wrong. Product outcomes remain the responsibility of the people who use the systems.
He is based in Lahore, Pakistan, where US Life Coaching operates. His publicly associated work includes leadership development, executive coaching, corporate training, and organised learning.
CTO
Chief Technology Officer
Usman Farooq is Chief Technology Officer of US Life Coaching. He is accountable for technology strategy, product engineering, and the reliable delivery of USLC’s digital systems. He joined USLC as Marketing Director in December 2024 and became CTO in February 2025. That sequence matters: he already understood how the company talks about development work before he took charge of how the software is built. His responsibilities include platform development, system reliability, and privacy-aware product design. Where AI appears in USLC products, he is responsible for implementing it as assistance under human oversight—organising information people provide and supporting optional next steps, not deciding employment, health, or eligibility outcomes.
The CTO’s relationship to USLC’s purpose is to translate human-development concepts into software people can actually use, while keeping the same limits the company states in public: user-directed inputs, clear purpose, and human judgement at the point of decision.
Before becoming CTO he worked in digital marketing, search, and web development. Those skills help USLC ship public experiences that stay usable. They do not replace the documented privacy, security, and responsible-AI practices published in the Trust Center.
USLC separates commercial direction from technical implementation without splitting accountability. The CEO sets what the company is for and what it will not become. The CTO turns that purpose into working products and refuses implementations that would cross the same line. Neither role can point at the other when a claim is wrong, a customer needs help, or a data request arrives.
Product stewardship sits with both. A system ships only when its learning purpose is clear, its inputs are chosen by the person using it, and a human remains responsible for interpretation. If a requested feature would turn a development tool into candidate selection, covert monitoring, or clinical care, leadership’s job is to decline it—even when the request is commercially attractive.
Privacy and data practices are a design constraint, not a legal appendix. They shape what is collected, why it is needed, and how someone can ask for access, correction, or deletion. Security, billing, refunds, and cancellation follow the same rule: publish what exists, and do not decorate the gaps with badges or invented service promises.
Evidence and claim review is a standing duty. Public copy, product language, and customer terms should agree. Unsupported statistics, awards, and outcome guarantees are not a growth tactic. Continuous improvement means changing the product when use, privacy, or evidence shows a limit. Human oversight closes the loop: support, complaints, and high-impact questions escalate to people, not to a model.
Usman Sana owns the company’s purpose, organisational priorities, and customer commitments. He is the named executive for what USLC will build, how it describes that work, and how a concern is handled when trust is at stake. He does not guarantee a development outcome for any individual, team, or organisation.
Usman Farooq owns technology strategy, platform quality, and the way AI is implemented inside USLC systems. He is the named executive for reliability, privacy-aware design, and keeping software within the company’s stated limits. Implementation choices still have to match the purpose the CEO is accountable for.
Named leadership is not a substitute for written practice. Privacy, responsible AI, security, billing, refunds, cancellation, and support are documented so customers and reviewers can check the standard without relying on a biography. USLC does not claim certifications or compliance badges it cannot prove.
The desk reference for data, AI, security, and buying terms.
What we collect, why we need it, and how to make a request.
How assistance is supposed to work, and where people stay in charge.
Measures we will list only when they exist, and how to raise a concern.
What you should know before you pay, without invented windows.
Route an enquiry for sales, support, privacy, or billing.
Product help, complaints, and escalation that does not depend on marketing.
If you are assessing the company, planning a programme, or need a named follow-up, send a clear question. You can also compare the systems themselves or read the Trust Center first.
