Loading…
Loading…
About Taro
Taro started with a conversation between two sisters.
One of our founders has a sister who’s an in-house lawyer in Nigeria. After work, she’d often be completely exhausted, sometimes getting home incredibly late.
So she started asking questions.
What exactly was taking so much time?
A lot of it wasn’t the legal work itself. It was everything around it. Keeping track of matters. Following up with external counsel. Watching agreement deadlines. Updating work schedules. Pulling information together when management needed a report.
Then she asked her sister a simple question:
“What parts of your job have you ever wished software could just do for you?”
She laughed.
And then she started listing them.
That conversation became the beginning of Taro.
We mapped how her team actually worked, built around it, took it back, and asked, “Would this actually work?”
Then we kept listening.
Conversations with in-house lawyers and legal leaders across some of Nigeria’s largest financial institutions showed us different versions of the same problem: court orders arriving in volume, transactions moving between teams with little visibility, external counsel updates being chased through email, agreements approaching expiry, and management reports being manually pulled together from work the team had already done.
The lawyers knew how to do the legal work. Too much of their time was being taken by everything around it.
That’s what we’re building Taro to change.
Our founders bring experience across legal technology and African financial infrastructure — including working closely with lawyers inside one of the world’s leading legal technology companies and building banking technology in Africa.
But Taro isn’t being built from assumptions about how an in-house legal team should work.
It’s being built from how in-house legal teams across Africa actually work.
We keep taking what we build back to the people doing the job, asking what’s missing and changing what doesn’t reflect their reality.
That’s how Taro started. It’s still how we build.
Lawyers don’t need technology to teach them how to be lawyers.
They need better infrastructure around the work they’re already doing.
Less chasing. Less searching. Less remembering. Less manually piecing together information the team already has. More time being lawyers.
That’s why we’re building Taro.
And yes, we still want one particular lawyer to get home earlier.