Direction before output
Clarify the workflow, constraints, and decisions a product must support before committing to a build.
MAHMOUD MOHAMED ATTIA · FOUNDER & PRODUCT ENGINEER
I build digital products that make complicated operations feel clear.
I’m the founder of Kepler Dev, based in the United Kingdom and Cairo, Egypt, and working with teams across the GCC and beyond. I bring product thinking and engineering together—from understanding the workflow to designing, building, and delivering the system behind it.
- Based in
- United Kingdom and Cairo, Egypt
- Working with
- Teams across the GCC and worldwide
- Focus
- Connected mobile, web, and operational products
- Involvement
- Discovery through delivery
Founder note
I started Kepler Dev because too much product work ships without anyone really understanding the operation it has to serve.
I have spent the last several years inside connected products — loyalty platforms, payment workflows, operational dashboards, internal tools — and the same pattern keeps appearing. The product is built; the workflow is not. People end up bridging the gaps between systems that were never designed to work together. Kepler Dev exists to address that directly: bring product thinking and engineering to the same conversation, and stay accountable from discovery through delivery. The work is small by design. Each engagement is one product, one founder-led team, and a clear scope that holds.
Selected experience
Work I have led end to end, with one confirmed public reference.
Client work
Glitre Loyalty Platform
A fuel-station network had no way to know its repeat customers. Every fill-up was a transaction; none became a relationship.
Read the case study
Additional private engagements are not listed publicly. Selected work can be discussed in a project review.
What clients work with me on
Four stages, one accountable lead.
Discovery
Map the current workflow, the people involved, the systems already in place, and the outcomes that would actually change the work.
Product direction
Translate the workflow into a clear product scope, a defensible architecture, and a delivery sequence a team can act on.
Technical delivery
Build the connected surfaces, services, and integrations with direct technical ownership through each release.
Accountability
Remain the single point of contact and the person accountable for the decisions, the build, and what happens after launch.
Background
A short record, with no invented dates.
- Present
Founder of Kepler Dev
Founder-led studio for connected mobile, web, and operational products. Discovery through delivery, single accountable lead.
- In progress
B.Sc. candidate, Computer Engineering — Cairo University
Undergraduate study at Cairo University. Degree not yet completed.
- Prior
Selected product and engineering work
Connected loyalty, payment-adjacent, and operational platforms. Details can be discussed in a project review.
Earlier roles and engagements are summarised only when the facts are verifiable. Anything pending confirmation is marked as such.
Principles
Three connected principles.
Systems that fit the work
Connect the parts of an operation that currently force people to bridge gaps manually.
Technical ownership
Keep the architecture understandable, deliberate, and ready for its next useful iteration.
Project review
Have a workflow that should work better?
Share the current situation and the outcome you need. Mahmoud will review the context personally before the first conversation.
Request a project review