Question 1

What types of businesses do you work with?

Accepted Answer

Mostly founders, operators, service businesses, agencies, and small teams that need a cleaner website, CRM, automation, dashboard, or AI-assisted workflow.

Question 2

How does the process work from start to finish?

Accepted Answer

Intake first, then a focused review, written scope, build, QA, launch, and handover. Nothing starts until the practical workflow and acceptance criteria are clear.

Question 3

What happens on the discovery call?

Accepted Answer

We walk through the current tools, bottleneck, lead path, handoffs, risk points, and what should happen after the build is live.

Question 4

Do I need to be available during the build?

Accepted Answer

Only at key checkpoints. Most of the work should happen from a clear scope, shared access, and concise review moments.

Question 5

How do you handle project handover?

Accepted Answer

You get a plain-language walkthrough, notes on what was changed, where to monitor it, and what to do if a provider or workflow changes later.

Question 6

Do you work with international clients?

Accepted Answer

Yes. Work is remote and scheduled around practical timezone overlap.

Question 7

What information do I need to provide to get started?

Accepted Answer

The intake asks for the services you need, current tools, business context, pain point, budget tier, timeline, access limits, compliance concerns, and contact details.

Question 8

Can you work on urgent timelines?

Accepted Answer

Sometimes. Urgent work has to be smaller, better defined, and realistic about access, review time, and provider constraints.

Question 9

Can you audit before building?

Accepted Answer

Yes. Audit-first is the preferred path when the current system is messy or the right build is not obvious yet.

Question 10

How are priorities chosen?

Accepted Answer

The first priority is the smallest reliable change that reduces confusion, missed leads, manual work, or owner blind spots.

Question 11

Can you work with an existing designer or developer?

Accepted Answer

Yes, as long as ownership, access, review process, and deployment responsibility are clear.

Question 12

How much does it cost?

Accepted Answer

Every project is scoped after intake. Public package tiers describe shape and depth, not guaranteed final pricing.

Question 13

Do you charge hourly or project-based?

Accepted Answer

Project-based is the default for defined builds. Open-ended support or investigation can be scoped separately.

Question 14

Can I pay in stages?

Accepted Answer

For larger scopes, milestone payments can be defined in the written scope.

Question 15

Is there a minimum project size?

Accepted Answer

There is no public fixed minimum. Tiny one-off tasks are accepted only when they are clearly useful and not better handled inside a larger cleanup.

Question 16

Do you offer performance-based pricing?

Accepted Answer

Not by default. Any incentive structure would need clean attribution, realistic baselines, and a written agreement.

Question 17

What is included in the project price?

Accepted Answer

The scope defines deliverables, testing, launch support, documentation, and handover. Third-party subscriptions or usage costs are separate.

Question 18

Do you offer refunds?

Accepted Answer

The written scope controls delivery. If something agreed is not delivered, the first response is to fix or reconcile it directly.

Question 19

Are there recurring fees?

Accepted Answer

Not by default from HMX Zone. Ongoing maintenance is optional; platform costs are paid to the platform providers.

Question 20

Do package tiers include revenue guarantees?

Accepted Answer

No. Packages describe work and deliverables, not revenue, ranking, conversion, or sales guarantees.

Question 21

Can scope grow after work starts?

Accepted Answer

Yes, but it is handled as an agreed change, not hidden scope creep.

Question 22

What CRM platforms do you work with?

Accepted Answer

GoHighLevel, HubSpot, Pipedrive, Salesforce, Airtable, Sheets, Supabase-backed workflows, and other tools with workable APIs or exports.

Question 23

Can you work with an existing GoHighLevel setup?

Accepted Answer

Yes. Existing accounts are audited first so live workflows are not disrupted casually.

Question 24

Do I need technical knowledge to use what you build?

Accepted Answer

No. The operating surface should be understandable to the team that has to use it.

Question 25

What tools and platforms do you use?

Accepted Answer

The stack depends on the workflow. Common tools include Next.js, Supabase, Vercel, GoHighLevel, HubSpot, Make, Zapier, n8n, Cal.com, OpenAI, Anthropic, Vapi, Twilio, and dashboards.

Question 26

Can you connect to any API?

Accepted Answer

Most APIs can be integrated when they have stable authentication, documentation, rate limits, and a practical event model.

Question 27

Do you build custom code or use no-code tools?

Accepted Answer

Both. Custom code is used when reliability, validation, data shape, or deployment control matters. No-code is used when it is faster and safe enough.

Question 28

Can you build full-stack websites and web apps?

Accepted Answer

Yes. HMX Zone builds Next.js and Supabase-style public surfaces with routes, forms, metadata, schema, analytics, and backend-ready data.

Question 29

Are you building your own CRM/SaaS system?

Accepted Answer

Yes. Product work informs how HMX Zone thinks about contacts, pipelines, messaging, billing, reporting, permissions, and operations.

Question 30

What if a third-party tool changes its API or pricing?

Accepted Answer

The system should include clear provider boundaries, monitoring, and a maintenance path for changes after launch.

Question 31

Can you clean and migrate existing data?

Accepted Answer

Yes, when the source data, target schema, privacy limits, and rollback plan are clear.

Question 32

Do you use Supabase?

Accepted Answer

Yes, especially for forms, public content, storage, moderation queues, and Postgres-backed operating data.

Question 33

Can you build dashboards?

Accepted Answer

Yes. Dashboards start with definitions and data freshness before visual polish.

Question 34

Do you write tests?

Accepted Answer

For meaningful workflows, yes. Tests and smoke checks scale with risk and route complexity.

Question 35

Can you work with webhooks?

Accepted Answer

Yes. Webhook work should include validation, retries or failure visibility, and safe handling of unexpected payloads.

Question 36

Can you deploy the work?

Accepted Answer

Yes, usually through Vercel or the current hosting provider, with environment variables and checks documented.

Question 37

Can you integrate payments?

Accepted Answer

Yes, when the payment flow, fulfillment handoff, notification logic, and refund or failed-payment cases are scoped.

Question 38

What kind of AI agents do you build?

Accepted Answer

Voice, chat, SMS, email, reply-drafting, lead qualification, support triage, call summary, and internal routing agents.

Question 39

How does an AI calling agent work?

Accepted Answer

It follows a bounded script, asks approved questions, records outcomes, uses allowed tools, and escalates when confidence or policy limits require a human.

Question 40

Can the AI agent handle objections?

Accepted Answer

Only the objections that are explicitly scoped, tested, and safe for the business. Unclear moments should escalate.

Question 41

How do you prevent the AI from sounding robotic?

Accepted Answer

Shorter prompts, realistic scripts, provider testing, transcript review, and strict job boundaries help more than hype.

Question 42

Can the AI book appointments automatically?

Accepted Answer

Yes, if booking rules, availability, qualification gates, consent, and fallback paths are clear.

Question 43

What languages can AI agents support?

Accepted Answer

It depends on the provider, voice quality, latency, target language, and review process.

Question 44

How do you measure AI agent performance?

Accepted Answer

Useful measures include completion rate, escalation rate, booking handoff quality, failed tool calls, opt-outs, transcript quality, and owner review notes.

Question 45

How much does AI calling cost to run?

Accepted Answer

Usage costs vary by telephony, STT, TTS, LLM, call duration, and provider. Provider costs are checked during scope.

Question 46

Can AI reply to customers without approval?

Accepted Answer

It can for low-risk scripted flows, but sensitive or high-value replies should use human approval.

Question 47

Can you build chat agents for a website?

Accepted Answer

Yes, when knowledge sources, escalation, privacy, and CRM handoff are defined.

Question 48

Can an AI agent update the CRM?

Accepted Answer

Yes, if fields, permissions, validation, and review rules are set.

Question 49

Do AI agents need disclaimers?

Accepted Answer

Sometimes. Consent, disclosure, recording, and channel rules depend on jurisdiction and use case.

Question 50

Can you compare AI providers?

Accepted Answer

Yes. Provider choice should weigh latency, quality, pricing, tooling, logs, and failure behavior.

Question 51

Do you train custom models?

Accepted Answer

Most client needs are better solved with prompts, retrieval, tooling, and workflow design before custom model training.

Question 52

What happens after the system is built?

Accepted Answer

You get handover, launch notes, and a path for tuning or support if the workflow changes.

Question 53

Do you offer ongoing maintenance?

Accepted Answer

Yes, when the system needs monitoring, provider updates, new integrations, prompt tuning, or reporting.

Question 54

What if something breaks after launch?

Accepted Answer

The first step is to isolate whether the issue is code, provider behavior, credentials, data, or process drift.

Question 55

Can you train my team?

Accepted Answer

Yes. Training can be part of handover or scoped as a deeper operator walkthrough.

Question 56

Can the system scale as my business grows?

Accepted Answer

The work is designed to be extendable, but new teams, channels, rules, or volume may need a scoped expansion.

Question 57

Do you provide performance reports?

Accepted Answer

Dashboards or recurring summaries can be included when reporting is part of the workflow.

Question 58

Can you monitor form submissions?

Accepted Answer

Yes. Monitoring can include error events, rate-limit blocks, failed notifications, and lead status checks.

Question 59

Can you update copy after launch?

Accepted Answer

Yes, especially when copy changes are tied to better qualification or fewer confused leads.

Question 60

Can you help after a provider outage?

Accepted Answer

Yes, if the outage affects a system HMX Zone built or supports and the account access is available.

Question 61

Can you document the workflow?

Accepted Answer

Yes. Clear documentation is part of a maintainable system.

Question 62

Can you take over a broken build?

Accepted Answer

Often, but it starts with an audit so ownership, risk, and unknown dependencies are visible.

Question 63

Do you publish client data?

Accepted Answer

No. Public proof avoids private lead data, account screens, payloads, URLs, credentials, and client identifiers unless approval is explicit.

Question 64

Can proof be redacted?

Accepted Answer

Yes. Redaction is expected for workflows that touch private operations.

Frequently Asked Questions

Still have a question?