The senior network engineer your team doesn’t have.

1. A deployment that stalled halfway and nobody can finish.
2. Redundancy that only exists on paper: one box fails and everything goes down.
3. A network that grew without an architecture, and now nobody understands it.
4. Work done badly by whoever installed it — and your team is paying for it.
5. An integrator quote that seems out of proportion to what you need.
6. Outages that come and go, and nobody can say why.
7. A firewall rulebase no one dares to touch.
8. An SD-Access or ACI rollout that never got finished.

If one of these is yours, that’s the work I do.

• From architecture to command line

  The person who designs your network is the person who configures it. Nothing gets lost between a consultant’s slides and a technician’s keyboard.

• Tested in a lab before it touches your network

  Changes and migrations are rehearsed first in a lab with real vendor images, so the maintenance window holds no surprises.

• Independent

  I don’t sell boxes or licences, and there’s no integrator margin on top. You pay for engineering hours, and the recommendation is the one that fits your network.

• Your part-time network engineer

  After the first problem, many teams keep a monthly bank of hours: a senior engineer on call for changes, questions and escalations, without hiring one.

• Remote by default, in person when it helps

  Day-to-day work happens over secure access that you control and can revoke at any time: faster, and no travel costs. Consulting, architecture and engineering all work remotely. If you’re in the Lisbon area and prefer to sit down for a kick-off, a workshop or a design review, I’m happy to meet in person.

• Every change documented

  Diagrams, configuration notes and the reasoning behind decisions, so your team is never dependent on me.