Field force software built by people who have watched the field work
Total Pharma Tech is an early-stage company building one platform for pharma field planning, compliant engagement and field intelligence. This page explains why we started, how we work with the organisations that partner with us, and where the product honestly stands today.
The field is measured on outcomes and equipped with fragments
In most pharmaceutical commercial organisations, the field team carries the clearest accountability in the business. Coverage, frequency, call quality, adherence to the plan and, ultimately, effectiveness against target are all measured at the level of the individual representative and the individual territory.
The tooling rarely matches that accountability. It is common to find territory design running in a specialist planning application, customer records and visit history in a CRM, targeting and segmentation in a spreadsheet maintained by one person in the commercial excellence team, compliance checks in a country-specific process, and reporting assembled by hand at the end of every cycle.
Each of those systems is defensible on its own. Together they create predictable problems. Data is reconciled rather than used. The representative becomes the integration layer, re-keying the same information into more than one place at the end of a working day. Managers coach against a view of the field that is weeks old. Commercial leadership makes resourcing decisions on numbers nobody can fully trace back to a source.
That is an industry observation, not a criticism of any one organisation. It is the natural result of two decades of point solutions, regional autonomy and systems that were never designed to share a data model. We started Total Pharma Tech because the fix is architectural rather than incremental: planning, execution, compliance and analytics have to read and write the same underlying field data, in one place, with one set of rules.
Everything in the product follows from that. If a feature would force a field team back into a spreadsheet to complete a task, it does not belong in the platform.
Three things shape every decision we make
These are not values on a wall. They decide what we build, what we refuse to build, and how a deployment is judged.
Field-first design
The product is designed around how representatives actually work, not how a head office process diagram says they should. That means a mobile workflow that survives a car, a clinic corridor and a hospital with no signal.
Offline capability is a baseline requirement rather than a premium feature. Call plans, visit records, forms and approvals all work with no connection, and sync intelligently when the device returns to coverage. Screens are built for one-handed use and for users who are not sitting at a desk.
Compliance by design
Interaction rules, disclosure requirements and data protection obligations differ by country, by affiliate and often by product. We treat those differences as core requirements of the data model rather than configuration bolted on at the end of an implementation.
Auditability is designed in from the first write: who changed what, when, and on what basis. Regional data residency options, role-based access, configurable retention and exportable audit trails are part of the platform, not a services project. Where a certification is not held yet, we say so plainly and label it as roadmap.
Measurable outcomes
Every deployment begins by agreeing what success will look like and how it will be measured. Coverage against a defined target list, call plan adherence, time from visit to validated record, reporting turnaround, data quality at the territory level — the exact measures depend on your priorities, but they are written down before configuration starts.
We review against those measures on a fixed date and share the result, including where the platform did not perform as expected. A pilot that cannot be evaluated is not a pilot, and we would rather end an engagement with a clear finding than continue without one.
Where we are today
We are an early-stage company. You should know exactly what that means before you spend time with us, so here it is without a marketing gloss.
An early-stage company, working in the open
- We are building the platform now. Total Pharma Tech is an early-stage software company. The product is functional and in active development, and it improves on a short release cycle driven by what pilot teams need next.
- We work with design-partner organisations. A small number of pharmaceutical and life-science teams use early builds with us, influence the roadmap directly and get close access to the engineering team in return. We do not name them publicly, and we do not present them as reference customers.
- Our security posture is documented, and its limits are stated. Encryption in transit and at rest, role-based access control, audit logging, configurable retention, tenant isolation and regional data residency options are available today. We do not hold ISO 27001 or SOC 2 certification at this stage. That work is on the roadmap and we will tell you exactly where it stands.
- Capability tiers are labelled. Where a feature is generally available, we say so. Where it is in pilot, in development or planned, we label it as roadmap. "Roadmap — ask us" is a real answer and it means the feature is not something you can rely on this quarter.
- We would rather show a working sandbox than a slide deck. Give us your territory structure and a description of your data and we will configure a sandbox you can click through. A demo that looks like your organisation is more informative than any deck we could write.
A note on diligence: if you are evaluating vendors and need evidence, ask us for it directly. We will give you the current position on certifications, subprocessors, hosting locations and the security questionnaire rather than a claim we cannot support.
We are also honest about size. We are not a large vendor with a global implementation army. What we offer instead is direct access to the team that builds and runs the platform, and a strong incentive to make every deployment succeed.
How we work with you
Four stages, each with a defined output and a clear list of what we need from your side. Nothing starts before the previous stage is complete.
Discovery and scoping
A working session with your commercial and IT stakeholders, usually sixty to ninety minutes. We map your territory structure, therapeutic areas, field roles, current systems and the countries involved, then identify where the real friction sits.
What we need from you: a territory or region list, the number of field representatives and managers, the systems you run today, and any country-specific interaction or approval rules we must respect.
Structured pilot with agreed success measures
Before any configuration, we agree two to four measures that will tell both sides whether the pilot worked, and the date on which we will review them. We then configure a sandbox using your data structure and your targeting rules.
What we need from you: a sample data extract or an agreed synthetic equivalent, a named pilot lead who can make decisions, and a small group of representatives and managers who will test in real conditions.
Deployment and data load
We configure rules per country or affiliate, load master data, connect your CRM, HR or data warehouse through API or file exchange, and run training for field users and managers. Rollout is staged country by country so each market can be validated before the next goes live.
What we need from you: an IT contact for SSO and integration, a data protection or legal contact to complete the DPA, and a training window that does not collide with a reporting cycle or a major launch.
Review and scale
On the agreed date we review performance against the pilot measures and share the findings in writing, including what underperformed. From there you either extend to further countries and teams, adjust the configuration and continue, or stop — with your data exported and returned.
What we need from you: manager time for the review session and a decision on the next set of countries or business units, so that scaling is planned rather than improvised.
Principles we hold ourselves to
These commitments apply to the platform, to our commercial behaviour and to everything we say in a sales conversation or a proposal.
Honest claims
We describe what the platform does today and label everything else as pilot, development or roadmap. We do not claim certifications we do not hold, and we do not present projected results as achieved ones.
Data minimisation
We collect the minimum field data required to run planning, engagement and reporting. We do not build shadow profiles, and we do not require patient-level data to deliver field force functionality.
Human review over automated decisions
AI output is advisory. Recommendations about targets, priorities or performance are reviewable by a manager, can be overridden, and the override is logged. No employment or incentive decision is made solely by a model.
No shared-model training on your data
Your commercial data is not used to train models shared with other customers. Where we use a third-party model provider, it operates under contract on your tenant's data only, and AI features can be disabled per affiliate.
Transparent pricing
Per-representative pricing is published on our pricing page, volume tiers are explained before you commit, and onboarding or data migration services are quoted separately with the scope attached. No usage surprises.
Exit without lock-in
You can export your data in open formats at any time during the contract, and on termination we provide a complete export of your records plus any audit trails you need to retain. Leaving should be an administrative task, not a project.
Careers and collaboration
We are a small team and we hire deliberately, usually when a specific piece of work needs an owner rather than against a fixed list of open positions.
The areas we most often need people in are field force consulting and commercial excellence, software engineering across backend, mobile and data, and customer success for implementations in the field. We also work with independent consultants and regional partners who already support pharma commercial teams in their market.
If your experience sits in one of those areas and the problem described on this page is one you want to work on, write to hello@totalpharmatech.com with a short note about what you have done and what you would like to do next. We read every message and reply when there is a genuine fit, even if there is no role open at that moment. You can also reach us through the contact page if you would prefer to start with a conversation.
See the platform with your own field structure in it
Send us your territory structure and a sample of your data shape. We will build a working sandbox around it and walk you through it, including the parts that are still on the roadmap.