Founding & leadership

Name
Stephan Lachmund, M.Sc.
Role
Founder & Amazon Connect consultant, CX-Routes
Experience
10+ years at Amazon (Systems Engineer II)
Education
M.Sc. Electrical Engineering and Information Technology
Coverage
DACH focus, EU-wide · remote and on site

Why Connect

An Amazon Connect rollout rarely fails because of the cloud. It fails because of the telephony underneath: number porting, SIP trunks, session border controllers, and the fact that the old PBX still has to run for another three weeks during cutover.

That is exactly where we come from. Over ten years at Amazon, a large part of it on voice infrastructure: Broadworks, Audiocodes, SBC, SIP – including migrating corporate sites from legacy telephony to VoIP. Plus AWS architecture and AI integration from the same hands-on practice.

This combination is rare. Cloud consultants know AWS but not telephony. Telephony houses know SIP but not Lambda. CX-Routes deliberately sits in between.

Specifically, we work with Amazon Connect Customer – the contact centre solution within the Amazon Connect portfolio.

Certifications & expertise

Presented transparently – including what is still outstanding.

AWS Certified
Solutions Architect – Associate
Cloud architecture, EC2, S3, Lambda, VPC
AWS Certified
AI Practitioner
Bedrock, GenAI fundamentals, ML services
AWS Knowledge Badges
Amazon Connect Communications Specialist – in progress
Amazon Connect Developer – queued · AWS training badges, not a certification
Broadworks
Enterprise telephony
Platform configuration & integration
Cisco Certified
Voice & networking
Audiocodes, SIP, RTP, SBC
Security & GDPR
Compliance practice
Permission models, recordings, audits

AWS partner status

Partner tiers in the AWS Partner Network are tied to certifications and documented customer wins. We currently hold no partner tier – here is the honest current state and the planned trajectory.

Planned: from 11/2026

APN registration

Services Path in the AWS Partner Network – access to partner resources, training and referral structures. Registration will follow when operations commence on 1 November 2026.

Planned: 6–12 months

Select Tier

Requires technical and business certifications spread across at least two people – therefore tied to building out the team.

Target: 18–36 months

Connect Customer Competency

The highest specialisation tier for Amazon Connect Customer. Requires validated partner status, a technical audit and documented customer wins.

For AWS partners: until the competency is in place we also work as subcontractors for existing Connect partners – white-label, with clearly defined roles.

Technical skills

Amazon Connect Customer

Instance & routing
Contact flows / IVR
Lambda integration
Contact Lens / Agent Assist

AWS & automation

AWS core services
Amazon Lex / Bedrock
Kinesis / analytics
Terraform / IaC

Telephony & security

SIP / RTP
Audiocodes / SBC
Broadworks
GDPR / security

Career

10+ years

Systems Engineer II · Amazon

Cloud infrastructure, VoIP systems and AI integration in global IT environments.

Focus areas

Voice migration and AI on AWS

Migrating corporate sites to VoIP (Broadworks, Audiocodes, SIP), plus building a chatbot on Amazon Bedrock that answers questions about internal documentation.

From November 2026

Founding CX-Routes

Independent specialist consulting for AWS Amazon Connect – strategy, migration, integration and operations for mid-market organisations in DACH and the EU. Operations commence on 1 November 2026; enquiries and bookings are welcome now.

Our principles

An honest assessment

We do not sell licences. If Amazon Connect is the wrong choice for your case, you will hear it in the intro call – not in the third month of the project.

Security & privacy from the start

Contact centres process personal data and recordings. Permission and retention concepts belong in the design, not in the follow-up.

Transparent pricing

Price ranges are published openly on the services page. Fixed fee where scope is clear, hourly where it is open – no negotiation theatre.

Enable, don't lock in

Your team should be able to run the platform itself. Documentation and briefing are part of the project – a retainer is an offer, not a dependency model.

Let's talk

An intro call costs you nothing but 30 minutes – and gives you a solid assessment.