Skip to Content

One person. Two disciplines.
No limits.

AMQ x Rafco is a boutique consulting and engineering practice — where strategy and execution are never separated.

identity — whoami
$
The Person Behind the Practice

AMQ and Rafco are not two people — they are one.

Ali is the person behind both names. AMQ is the consulting mind — analytical, strategic, business-first. Rafco is the engineering identity — technical, precise, execution-driven.

Together, they are how one person thinks through a complete problem.

AMQ
AMQ Consultants
The consulting lens
  • Asks why before how
  • Maps the business first
  • Designs the solution architecture
  • Owns the strategy
  • Speaks the client’s language
Ali
RF
Mr Rafco
The engineering lens
  • Builds what the strategy demands
  • Writes clean, scalable code
  • Engineers the data layer
  • Owns the execution
  • Speaks the machine’s language

“Most consultants can’t build. Most developers don’t consult. I do both — not by wearing two hats, but because I genuinely think in both languages. AMQ and Rafco are the same person at different points in the same problem.”

— Ali · Founder, AMQ x Rafco

Two identities. One standard.

AMQ
AMQ Consultants
Consultant · Architect · Analyst
Business consulting BI design Workflow strategy Odoo architecture Data structuring

Specialises in understanding business challenges before reaching for solutions. Frames requirements, designs processes, and ensures every technical decision is grounded in commercial logic.

RF
Mr Rafco
Developer · Engineer · DevOps
Odoo development Automation BI engineering SQL & data DevOps

Builds what the strategy demands — custom Odoo modules, automated workflows, SQL-powered dashboards, and robust infrastructure. Clean code, scalable architecture, version-controlled everything.

founding-principles — git log --oneline
a3f21c9 strategy-first — diagnose before we prescribe; no tool pitched before the business is understood
7b18e42 architect-then-build — systems designed holistically; no retrofits, no technical debt by design
f92d310 outcomes-over-output — measured by business impact, not deliverables shipped

One mind, zero handoffs

Consulting and engineering usually live in different heads, on different timelines, with different incentives. Here they don’t.

01
No translation layer

When the consultant and the engineer are the same person, nothing is misinterpreted. Requirements become implementations without a game of telephone between teams.

02
Accountability end-to-end

We own the problem, not a phase of it. From diagnosis to deployment, the same mind is responsible for the outcome — which means no one to blame but ourselves.

03
Boutique by design

We work with a select number of clients at a time. Not because we can’t scale — because quality requires attention, and attention requires limits.

Interested? Let’s Talk

Ready to work with us?

Tell us about your challenge. We’ll tell you how we’d approach it — honestly, and without the sales pitch.