The moment this becomes a real problem is when a regional payroll bureau or HR software reseller signs a mid-market client who needs time tracking, demos one of the major tools, and watches the deal stall because the client's ops manager says the interface 'looks like it was built in 2011' or asks for a view their specific crew type needs that the template doesn't support. The reseller can't fix the upstream product. They lose the deal or lose the client six months later.

The gap persists because the major time tracking vendors sell direct and their incentive is to standardize, not to give resellers a way to differentiate. Template-driven modules exist precisely because customization at the individual client level is expensive to support at scale — so the vendor locks it down and calls it a feature. The buyer (the reseller or the HR admin who bought the software) is different from the user (the shift worker or field technician), so the person who hates the interface doesn't have budget authority, and the person with budget authority never touches the UI.

What the current products get wrong, anchored to the actual complaints: the display density is fixed ('a slightly less condensed display would be cool, maybe offering the choice would be good'), CSS is hardcoded with no way to inject styling ('their CSS could use some work'), and mobile schedule creation is a second-class experience. These aren't bugs — they're structural decisions that the vendor has no incentive to revisit for any one client.

This is a business and not a feature because the need recurs at every new client the reseller onboards. Each new client has a different brand, different density preference, different mobile vs. desktop split. A reseller closing 10 clients a year and losing 2 of them to UI objections is losing real revenue. The cost is concrete and repeats.

What to build

Build a white-label time tracking front-end — configurable layout density, brand theming, dark mode, and mobile schedule view — that connects to existing time tracking data APIs and ships as a reseller-deployable web app with per-client configuration stored separately from the upstream system.

Where to start

Start with resellers who already use one specific time tracking API (pick whichever has the most documented public API and the most visible reseller complaints) and offer to build the first client's white-label UI at cost in exchange for a public case study and a referral intro.

The hard part

You need resellers to trust you with their client relationships before you have a track record, which means your first few customers have to be ones where you can get a warm introduction through an existing payroll or HR software ecosystem — cold outreach to resellers won't convert early.

How it makes money

Monthly fee per active client instance the reseller deploys, with a one-time setup fee per client for custom theming — resellers pass the cost through to their clients as a branded product.

See the evidence. The complaints behind this idea, the products they came from, and similar ideas in Time Tracking.

More ideas in Time Tracking