How I Work

I believe in building first, talking second.

My Approach

Understand the Problem

Before writing any code, I need to understand what you're actually trying to solve. Not what software you think you need — what business problem you have.

Propose a Clear Solution

Based on your constraints (budget, timeline, existing systems), I suggest an approach. Sometimes that's a custom build. Sometimes it's a simple automation. Sometimes it's "you don't need me for this."

Build a Focused Prototype

For most engagements, I recommend starting with a small, paid pilot. This lets you evaluate my work without a large commitment.

Iterate Based on Feedback

I work in short cycles with regular check-ins. You see progress early and often.

Deploy & Document

When the project is done, I make sure you know how to use it. Documentation, training, whatever you need.

What I Don't Do

Rush jobs without proper scope
Vague requests without clear requirements
Work without upfront payment
Promise things I can't deliver

Communication

Primary: WhatsApp, Email

Meetings: Zoom, Google Meet (when necessary)

Location: Douala, work remotely worldwide

Response time: Usually within 24 hours

Why This Approach?

I prefer being evaluated on real work, not claims. The pilot model protects both of us:

You evaluate actual work, not promises
I understand your real needs, not assumptions
We build trust through demonstrated results