Daskul is a founder-run software studio. I've built and run Klei — a SaaS for learning centers — and do product engineering for a South African fintech. When your operations run on spreadsheets and tools that almost fit, I build the software that actually solves it.
I design and engineer the systems off-the-shelf software can't handle — then stick around to maintain and grow them.
I build around how your business actually works — your data, your rules — not the other way around. The point is to retire the spreadsheets and the one stopgap everyone's scared to touch. You own the code and the database outright.
Multi-tenant platforms, internal dashboards, the customer-facing app itself. I've taken software from rough prototype to a product that charges real cards every day. The parts that fail silently — auth, billing, tenant isolation — surface months later when one customer sees another's data. I get those right the first time.
You're a founder staring down a technical call with nobody senior to argue it out with: rewrite or limp along, will it hold at 10x, build or buy. That's me. I give you a straight read, including "don't build this yet," and I'll write the code afterward if you want.
Launch is when the real bugs show up. I watch the errors, fix what users actually hit, and ship the next round as new edge cases surface. Most software rots six months after handoff because nobody owns it. I don't hand off and vanish.
My own SaaS, built for tutorial centers and basic-ed schools. Klei brings students, programs, scheduling and billing into one platform — proof of what I ship when I own a product end to end.
Daskul is a founder-run software studio in the Philippines — and that's me. I design and write the product myself, so when you ask why something works the way it does, the answer comes from the person who decided it. Fewer people in the loop means decisions in hours, not a week of meetings. I have strong opinions and I'll use them: if a spec is going to hurt your users, I'll say so and offer something better. I'd rather argue with you for an hour than build the wrong thing for three months.
The person who scopes your project is the one who writes the code. No translation layer, no telephone.
I won't quietly build a spec I think will fail your users. I'll say so and propose something better. Klei is where I proved it.
Proven choices, documented as I go, so it stays easy to extend — whether I keep running it or you take it in-house.
Honest reads on cost and timeline, even the unwelcome ones. You always know where your project stands.
A few sentences about the problem, or the half-formed idea, is enough to start. I'll write back — and if it's not a fit, I'll tell you and point you to someone better suited.
Goes straight to my inbox — no forms, no autoresponders. I read every message myself and reply personally.