Skip to main content
Clinton Agada
About · Founder & CEO, Veraclins Tech Solutions

A senior engineer who went and started the company.

I started writing software in 2017. Eight years as an engineer — mostly remote, mostly senior, including a stretch at Andela — taught me where systems break and what it costs to keep them boring. In 2025 I founded Veraclins Tech Solutions to build a few of my own. I'm the founder and CEO, and I'm still the one in the codebase.

Section01

How I think about building

Four principles I hold as an engineer, and now as a founder — each one something I've been wrong about at least once. The case in the right column is where I learned it.

01

The interesting decisions are made at the seams

Whether you're embedding bpmn-js inside React, or running Mongo and Postgres at the same time during a migration — the parts of the system that matter live at the boundary between two things that don't quite agree. I plan for those first; the rest is plumbing.

Where I learned this

The two-database phase of the Mongo → Postgres migration. The schema was the easy half.

02

A design system is a set of decisions, not a set of components

40 components is the artefact. The real product is "we agreed how date pickers behave when the locale flips, and we wrote it down." If a maintainer can't answer that without reading source, the system is going to fork itself in 18 months.

Where I learned this

Building the in-house design system that Edulinks.ng now runs on. Every shortcut I took in year one I paid for in year two.

03

Boring is a feature, not a personality

I prefer Postgres to whatever is on the front of Hacker News this week. I prefer CVA to a clever class-name DSL. I prefer the framework the team already knows. Novelty has to earn its way in by solving a real problem, not by being new.

Where I learned this

Two rewrites, both abandoned at 70%, both because we picked the new tool first and the requirements second.

04

The README is part of the codebase

Every commit to a load-bearing piece of code that doesn't update the docs is a commit that's slowly making the system harder to staff. I write the migration playbook before I run the migration.

Where I learned this

A 30-page playbook for the BPMN editor cutover. The playbook saved the cutover when I was on holiday.

Section02

Two ways to work with me

Both in my own name, both engineering only. Advisory is judgment; consultancy is hands-on. Team-scale or long delivery is Veraclins.

Advisory

Judgment, by call — when you need a decision, not a deliverable.

  • +Architecture and system-design calls — what to build, what to buy, what to defer.
  • +Tech-stack and code-level decisions you keep going back and forth on.
  • +Hiring into engineering — what to look for, how to shape the team.
  • +Single calls, or a monthly cadence with light async in between.

Consultancy

Hands-on, when you need the work built — and want it built by someone senior.

  • +Design systems, migrations and editors — the load-bearing work, scoped and shipped.
  • +Embedding third-party canvases (bpmn-js, monaco, tldraw) in React, cleanly.
  • +The migration playbook, the maintenance contract, the on-call doc — written, not just advised.
  • +Select, senior-led engagements. Team-scale builds route to Veraclins.

The lineBoth are engineering only — fundraising, sales strategy, hiring outside engineering and legal are a clean no. Equity-only deals or long retainers are case by case. And nothing here pulls me off Veraclins: bigger or team-scale builds go to the company, with its people.

Section03

A short professional history

Roles I held long enough to ship something I'd still defend.

2025 — Now

Founder & CEO

Veraclins Tech Solutions

Building Edulinks.ng (launching July 2026) plus NairaBiz, JobSearch and Pitch Prophet. Running the company and still lead engineer on the parts that matter.

Abuja · NG
2023 — 2025

Lead engineer

Independent · building toward Veraclins

The in-house design system and the BPMN 2.0 editor — the work that became the foundation Edulinks.ng and the company were built on.

Remote
2018 — 2023

Senior engineer

Andela

Senior IC across distributed product teams. The zero-downtime Mongo → Postgres healthcare migration (infra cost down 30%+) ran in this era.

Remote
2017 — 2018

Software engineer

Agency · client work

React, Vue, Laravel. The year I learned to read other people's code under deadline pressure, which I still consider the most valuable skill I have.

Lagos · NG

On the handle"veraclins" is my online name from before the company existed — the same word on GitHub and LinkedIn, predating Veraclins Tech Solutions. So @Veraclins is me, the person.