What we’re building
White collar businesses depend on fragile, time consuming data entry to plan, record, and execute work. Client services firms (~$10B TAM) are especially dependent on this broken process: lawyers, accountants, and consultants need to faithfully track their time in order to get paid. Lawyers spend an hour per day tracking their time, and fail to account for 20% of their work.
Ajax frees hardworking professionals to do their jobs by passively capturing, analyzing, and preparing the reports they owe their boss/client/whoever.
Our results speak for themselves:
99% Customer Retention: firms that buy us stay with us (>90% annual is considered good)
96% Pilot Conversion Rate: when we start pilots, we win them (>70% is considered good)
Customers say things like (all real quotes):
“I’m going to leave my husband for Ajax”
“I was so bad at time tracking that I was going to have to switch careers until I found you”
“This is somewhere between 5,000 and 10,000 better than what I was doing before”
“This is the easiest money I’ve ever spent”
Designing this well is unusually hard. Our system is fundamentally cooperative; the product must fold into our users’ daily habits while fading into the background and - eventually - eliminating the task of timekeeping altogether.
The Role
Who you are
A designer with a portfolio of shipped products…
Who can operate independently as a designer and collaboratively with engineers…
And can turn dense, information-heavy workflows into delightful, fast experiences
What you’ll do
Talk with lawyers, firm administrators, engineers, and our go to market team; watch people actually work and then actually write time entries; identify problems worth solving
Define core trust loops for our customers: what is captured, how is it generated, and
Figure out the right abstractions for a firm intelligence platform atop our timetracking
Meaningfully contribute to team composition by interviewing designers and engineers
You’ll excel here if
Your reward function is customer happiness (stolen verbatim from our 2nd engineer).
You want ownership - that means work is done when it's live and our users are delighted,, not when it’s engineer-ready in Figma.
You like adventure. We’re solving an unsolved problem, so we need to be brave and rigorous in exploration. The optimal number of unsuccessful experiments is higher than 0.
Working at Ajax
How we work, in practice
Here’s a real sprint we had in November:
During a pilot with an important firm, the GTM team noticed that activation was low
We pulled some data from Posthog and Metabase and came up with a hypothesis: these users were the fastest billers we’ve ever seen, and Ajax’s entries weren’t ready for them in time
We restructured our React FE to show a Domino’s pizza style “entry in progress” tracker, assuring nervous billers that their work was indeed captured
Alex issued a native app update for our Flutter app that captured data more quickly when users task switch
Roger optimized some gnarly python async code to bring our p99 entry latency from ~180s to ~120s.
🎉 We won the pilot! 🎉
FAQs
Roger slept through his alarm and joined standup
Innovation that excites from Brandon
Tyler can be a lot