FAQ
Answers before the first conversation.
Start here if you are comparing service lanes, trying to understand the project process, or checking how Geek Hoppers handles AEM, support, pricing, and privacy.
Question routes
General
What does Geek Hoppers do?
Geek Hoppers builds websites, custom web applications, AI workflows, data dashboards, and Adobe Experience Manager systems for teams that need reliable digital engineering.
Who do you usually work with?
We work with founders, product owners, marketing teams, IT leaders, and enterprise platform teams that need design, engineering, migration, or support help.
Where are you located?
The studio is based in Noida, India, and works remotely with clients across time zones.
Digital Services
Do you handle both design and development?
Yes. A project can include UX, interface design, frontend, backend, integrations, deployment, and post-launch support.
What is the difference between a website and a web application?
A website is usually content and conversion focused. A web application includes richer workflows, accounts, data, dashboards, permissions, and integrations.
Can you work with our existing stack?
Usually, yes. We commonly work with React, Next.js, Astro, Node.js, Python, PostgreSQL, modern APIs, and cloud hosting, and we adapt when a client already has a maintainable environment.
Adobe Experience Manager
If your question is about AEM Sites, Edge Delivery Services, DAM, Forms, Commerce, or Cloud Service, start with an AEM service lane inquiry.
What AEM services do you provide?
We support AEM Sites, Edge Delivery Services, AEM Assets, AEM Forms, Commerce integration, AEM as a Cloud Service migration, component development, templates, and authoring systems.
Do you help with AEM migrations?
Yes. We can help plan and execute migrations from AEM 6.5, AMS, or other content platforms toward AEM as a Cloud Service or Edge Delivery Services.
What is the difference between AEM Sites and Edge Delivery Services?
AEM Sites is the enterprise CMS platform for structured authoring, components, templates, and content operations. Edge Delivery Services focuses on document-based authoring and high-performance edge delivery for suitable page types.
Process
How does a project usually start?
It starts with discovery: objectives, users, systems, risks, timeline, and the smallest useful version. If there is a fit, we turn that into a proposal and phased plan.
What do you need before starting?
A rough brief, known constraints, existing designs or documentation, access requirements, and any systems the build must integrate with.
Will we get a dedicated team?
For active projects, we assign clear ownership so context stays intact across design, engineering, reviews, and support.
Pricing & Timeline
What is your pricing model?
Pricing depends on scope. Defined builds can be fixed-fee. Exploratory, support, AEM, or ongoing product work often fits retainers or time-and-materials.
How long does a typical project take?
Focused websites can move in weeks. Web apps, AI workflows, data systems, and AEM programs usually need a phased plan over several months.
Do you offer a free consultation?
Yes. The initial discovery conversation is used to understand the problem and decide whether Geek Hoppers is the right fit.
Support
Do you provide maintenance after launch?
Yes. Support can include monitoring, dependency updates, performance work, bug fixes, content changes, security checks, and small feature releases.
Can you improve an existing website or app?
Yes. We can audit the current system, identify performance, accessibility, SEO, UX, or architecture issues, and propose a staged improvement plan.
Privacy & NDA
Do you sign NDAs?
Yes. NDA-friendly discovery is available before discussing sensitive business or technical details.
Who owns the code and assets?
Project ownership terms are defined in the agreement. Custom project deliverables are typically transferred after agreed payment milestones are complete.
Contact
How quickly do you respond?
For new project inquiries, we aim to respond within 24 business hours.
What should I include in the first message?
Share the outcome you want, the current state, timeline, budget expectations if available, and any links to designs, docs, or existing systems.
A rough question is enough if the constraints are honest.
The first conversation can start with uncertainty. What helps most is knowing the outcome, the current system, the timeline, and the decision you need to make next.