Partner with TeamTrek

We would rather integrate than replace.

TeamTrek sits beside the payroll, accounting and project tools a team already runs. Build a connection to one of them, sell TeamTrek in your market, or run it for the teams you look after.

  • A named contact, not a queue
  • A sandbox tenant that never expires
  • Margin, not a finder's fee

Teams buy this kind of software from someone they already trust.

Which is why most of the markets we are in, we are in through a partner. A partner’s first customer is usually live inside a month.

Teams and the partners who serve them

0
markets we sell in through a partner
0
integrations live, payroll and accounting among them
0 days
to a reply on an application, either way

Figures and company names shown for demonstration — replace with verified numbers and real partners before launch.

A product that has to be read by the people it measures.

That constraint is the reason teams keep TeamTrek, and it is the reason it is easy to recommend: nobody has to defend it to the people it tracks.

It survives the rollout meeting

Every member opens the same figures their manager sees, so the objection that kills most monitoring rollouts does not arrive.

100%of the record, readable by its subject

It fits what a team already runs

Hours leave as CSV and PDF, per person, project or client, in any range. Nobody has to move their payroll or their invoicing to adopt it.

CSVand PDF, any range

You keep the relationship

We do not go around a partner to the account they brought. Renewals, expansion and the quarterly conversation stay yours.

Yoursthrough renewal and expansion

Three ways to work with us.

Pick the one that describes what you already do — we will say if another fits better. Commercial terms are set per partner and are not published here.

Build

Technology partners

You build or run a system TeamTrek should hand hours to. We build the connection with you and document it on both sides.

Who it is forPayroll, accounting, PSA and sign-on vendors whose customers have to account for their time.

  • A sandbox tenant that never expires
  • REST API and webhooks, with the hours' source
  • We build the first connection with you
  • Documented and listed on both sites
Apply as a technology partner

Most partners start here

Sell

Solution and resale partners

You sell and set up software for teams in a market we are not in. You hold the contract, the margin and the account.

Who it is forResellers, consultancies and implementation firms who already sell business software in their market.

  • Partner price, with margin on renewals too
  • The contract and the account stay yours
  • Our demo script, objection notes and security answers
  • A named contact with a calendar, not a queue
Apply as a resale partner
Operate

Managed service providers

You run the tooling for the teams you look after. One console across tenants, with each team's record readable by that team.

Who it is forManaged IT providers and operations firms running the software several client teams work in.

  • One console across every tenant you run
  • Each team reads its own record, and only its own
  • One invoice across the tenants you operate
  • The rollout playbook we use ourselves
Apply as a managed service provider

Commercial terms, including margin and term length, are agreed per partner. Tell us which of the three you are and we will say if another fits better.

What a connection to TeamTrek is made of.

Five ways hours leave TeamTrek and identities come into it. A technology partner builds against one or two of them; a resale or managed service partner mostly uses what is already built.

REST API

  • JSON
  • Keyed
What it carries
Hours by person, project, task and client, each with the source it came from.
What it asks of you
A key, and a tenant to point it at.
GET /v1/hours?from=2026-03-01&to=2026-03-14Illustrative
{
  "member":  "maya.r",
  "project": "Atlas redesign",
  "task":    "Build",
  "minutes": 268,
  "source":  "offline-synced"
}

Webhooks

  • Events
  • Signed
What it carries
An entry approved, edited, or synced after a spell with no connection.
What it asks of you
An endpoint that answers inside two seconds.
POST https://your-app.example/teamtrekIllustrative
{
  "event": "entry.synced",
  "entry": {
    "member":  "maya.r",
    "minutes": 125,
    "source":  "offline-synced"
  }
}

Exports

  • CSV
  • PDF
What it carries
Any period, filtered the way the report on screen is filtered.
What it asks of you
Nothing: it is in the product already.
hours-2026-03-01_2026-03-14.csvIllustrative
member,project,task,date,minutes,source
maya.r,Atlas redesign,Build,2026-03-10,268,online
maya.r,Atlas redesign,Build,2026-03-10,125,offline-synced
jonas.k,Atlas redesign,Review,2026-03-10,90,manual

Sign-on

  • SAML
  • SCIM
What it carries
Who is on the team, and what each of them may read.
What it asks of you
A directory, and one metadata exchange.
POST /scim/v2/UsersIllustrative
{
  "userName": "maya.r@okafor.example",
  "name":     { "givenName": "Maya" },
  "active":   true,
  "groups":   [ "Engineering" ]
}

Sandbox tenant

  • Full
  • No expiry
What it carries
Seeded people, projects and a year of hours, in a tenant of your own.
What it asks of you
An email address. It never expires.
tenant: sandbox-okaforIllustrative
people    28 across 3 teams
projects  11, with tasks and clients
hours     12 months, online, offline, manual
resets    on request, never on a timer

Every route carries the rule the product carries: the people in a record can read what it says about them, wherever the hours end up. Payloads above are illustrative.

The same four things, whichever programme you are in.

Three of them land the day the agreement is signed. The fourth waits for a live customer, and says so.

  • A named contact

    A person with a calendar who knows your accounts, not a portal and not a queue.

    Day one
  • A sandbox that never expires

    A full tenant with seeded data for demos, tests and training, not a trial that ends mid-build.

    Day one
  • The material we use ourselves

    The demo script, the objection notes and the security answers, unedited.

    Day one
  • A listing on this site

    Your firm named on the pages customers in your market arrive on, in your own words.

    After your first customer is live

Where a partner makes the difference, and where we would be honest about it.

Where we need partners

  • Markets where buying software from a local firm is the normal way to buy it.

Where we do not

  • Anywhere a partner would be a layer between us and a customer with nothing added.

What we ask, either way That the record stays readable by the people it describes, wherever you sell it.

Three steps, and we tell you no quickly.

  1. 01

    Tell us what you do

    Who your customers are, what you already sell them, and which of the three programmes you think you are. The form further down this page is the whole application.

    Reply 2 days

  2. 02

    One call, both ways

    Thirty minutes. You see the product properly and we find out whether your customers have the problem it solves. Either side can say no here without it being awkward.

    Call 30 min

  3. 03

    Sandbox, terms, first customer

    The tenant and the material on the same day as the agreement. Most partners take a first customer live inside a month, because the rollout is short.

    To first customer ~1 month

What partners say the first year looked like.

Partner testimonials are placeholder content — real quotes from approved partners will appear here.

Fair questions,
before you apply.

Anything else? Write to us at .

Tell us who your customers are.

Six fields, one reply inside two working days, and a straight no if your customers do not have the problem TeamTrek solves.

  • No deck, no form-fill nurture sequence
  • A person reads it, and that person replies
  • Or write to partners@teamtrek.app

Every field is required. Nothing here is passed on to anyone outside the partner team.

This opens your own mail client with the answers written out, addressed to partners@teamtrek.app. Nothing is sent from this page.

Thirty minutes, and no deck.

If your customers do not have the problem TeamTrek solves, we will say so on the call rather than six months in.