Stay in Touch

I'd love to hear from you, whether it's a question about a post, a correction, an idea for a future article or a project you'd like help with.

Get in Touch

• Email: Madhusudhan.Goli@outlook.com
• WhatsApp: @Madhusudhan.Goli (message me with a short note on who you are and what you need)
• Based in: Hyderabad, India (IST), so replies may take a few hours if you're in another time zone

Where I can help

• AEM Sites development: components, HTL, Sling Models, dialogs and templates
• AEM Assets: DAM structure, workflows and processing setup
• Code and architecture reviews for existing AEM projects
• Dispatcher and caching reviews
• Technical leadership and mentoring for AEM teams
• Training sessions or workshops for developers new to AEM

How I work

• Remote, with regular written updates and agreed milestones
• Clear scope, timeline and payment terms agreed in writing before work starts
• Happy to sign an NDA where needed
• Rates depend on scope and duration, and I'm happy to discuss them once I understand the work

What to include in your enquiry

1. A short description of the project and your goal
2. Your AEM version (6.5 or Cloud Service) and the main tools involved
3. The timeline and how many hours or weeks you expect
4. Any constraints, such as time zones, tools or security requirements

Please email me for project enquiries. I'll reply with questions, availability and next steps. Because I take on a limited amount of outside work, I can't accept every request.

What I Can Help With on This Blog

• Questions about posts in any of the series
• Spotting an error or outdated information (please include the post title and what you found)
• Suggestions for topics you'd like covered
• Guest post ideas or collaboration on AEM learning content

Before You Write

• Be specific. Include your AEM version, what you tried and any error messages. It lets me give a useful answer faster
• WhatsApp is for quick questions only. For anything that needs code, logs or screenshots, please email me
• Never send passwords, tokens or client confidential details. Remove anything sensitive from logs and screenshots
• Response time: I aim to reply within a few days. Free advice on blog topics is best-effort, and I can't provide unpaid production support or review individual projects without an agreed engagement

Follow Along

Subscribe to the blog to get new posts by email as they're published.

I only use your details to reply to your message. The views on this blog are my own and don't represent my employer or any client.