Still a student. Building it anyway.

I'm Kareem. I run Ceptro on my own, I scope it, build it, and I'm still the one you'd email if something breaks.

Most of my time goes into automation, lead gen and data work, basically anywhere a business is doing something by hand that a bit of scripting and a few well-connected tools could handle instead.

I'm doing this while I'm still a student, and I'm not going to pretend otherwise. I don't have fifteen years of consulting behind me. What I've got is time, curiosity, and a habit of not stopping until I actually understand why something's inefficient.

Why Ceptro exists

I didn't start Ceptro with a five-year plan. I started it because I kept seeing the same thing: everyone talks about what AI can do, but almost nobody actually points it at something boring and real inside a business and just sees what happens. So that's what I do.

The tooling behind this work changed faster in the last two years than in the decade before it. That's genuinely inconvenient for firms with a decade of process built around older assumptions. It's also the single biggest advantage of starting fresh: I'm not maintaining a legacy way of doing things, so I can build with what actually works now.

I won't pretend that's the same as a long track record. It isn't. What I can offer instead is closer attention than a bigger shop would give you, on a smaller number of projects at a time.

I'd rather scope something small and prove it works than sell you a twelve-month transformation.

How I work

I like taking things apart. Give me a clunky process or a tool everyone complains about, and I want to know exactly where it breaks and whether there's a cleaner way through it.

Most of what I build starts as an experiment, not a pitch. I try something small, throw it at a real problem, and only take it further once it's actually holding up, not just working in theory.

I'd rather ship something narrow that genuinely works than something broad that sounds impressive and quietly falls apart.

What I care about getting right

I build against how your business actually runs, not a tidy demo, and I'm honest with you about where a system's limits are. The goal is a system you understand and trust, not a black box you're afraid to touch.

Studying, and building

Alongside all this, I'm studying Level 3 Travel & Tourism. Not exactly related to any of this, and that's kind of the point. I didn't come into Ceptro from a career already in tech. I'm building it from scratch, on the side, because I got curious enough to actually do something about it.

If that sounds like the kind of working relationship you want, I'd like to hear what you're dealing with.