Free App Consultation: What to Expect on the Call

What a free XenonApps consultation actually is

A free 30-minute scoping call is not a demo theater or a bait pitch. It is a structured working session so both sides can decide whether a build engagement makes sense.

You should leave with clearer scope, a realistic price band, and explicit next steps—not a vague promise that someone will send something someday.

We operate from 7969 NW 2nd Street, Miami, FL 33126, with US-hours overlap. Remote stakeholders are first-class participants on the same agenda.

Agenda we follow

1. Context (5 min): who you are, who the users are, what win means for v1.
2. Product walkthrough (10–12 min): must-have flows, platforms, integrations, constraints.
3. Risks (5–7 min): compliance, offline, store category issues, hiring constraints.
4. Band and next steps (5 min): which locked band fits ($15K–$30K / $30K–$80K / $80K–$200K+), what we need for a written SOW, whether NDA comes first.

If the conversation needs more time, we schedule a follow-up rather than rushing a fake certainty. Thirty minutes is enough to orient; it is not enough to pretend discovery is finished for a Band C system.

How to prepare (checklist)

• Primary user persona in one sentence
• Must-have versus nice-to-have list (even messy bullets)
• Platform preference and why
• Integrations inventory (CRM, payments, WhatsApp, EHR-adjacent APIs)
• Compliance notes—or none known yet
• Timeline pressure (launch event, seasonality, fundraising)
• Who can approve scope after the call
• Links to competitors or inspiration (optional but helpful)

What you should leave with

A band orientation, a short risk list, and whether we recommend custom mobile, Flutter or React Native, or (rarely) delaying build for no-code validation.

If we are not a fit, we will say so. If we are, you get a path to a written proposal—not pressure to sign on the call.

You should also know what artifacts we need next: user stories, API docs, brand assets, or a security questionnaire.

NDA and confidentiality

NDA available before you share sensitive material. We treat credentials and product ideas as client property.

Do not paste secrets into Calendly notes; use secure follow-up. Store credentials belong in a vault conversation, not a chat popup.

What we will not do on a free call

• Invent ROI percentages or competitor rankings
• Commit to a fixed ship date without discovery
• Design your entire product in thirty minutes
• Quote Band A for an obvious Band C system
• Pretend a marketplace is a weekend MVP

After the call

Typical follow-up within one business day: summary notes, band confirmation, and SOW prerequisites. Form submissions and phone use the same SLA spirit.

Miami visits at 7969 NW 2nd Street are by appointment when kickoff quality improves in person. Bring decision-makers if the product spans ops and customer experience.

If you need a 15-minute automation audit instead of a product build conversation, say so when booking—the shorter slot is for ops workflows, not full product scoping.

How this differs from a sales demo

We are not walking you through a canned slide deck about how innovative we are. The time is yours to pressure-test scope.

You are welcome to challenge assumptions. The goal is a shared picture of risk, not a theatrical close.

If you want portfolio proof, ask for specific case studies. We will point to qualitative lessons—Coin Counter, Bodynetic, Pharmassist Rider, Resfoody—without inventing KPIs.

Stakeholder tips

Prefer one decision-maker plus the person who knows the workflows. Large silent audiences make prioritization harder.

Finance partners are welcome when bands need defending. Engineering partners are welcome when repos exist.

If you are comparing three vendors, tell us. We would rather compete on clarity than on theater.

FAQ

Is the call really free?

Yes. You are not billed for the scoping conversation.

15-min versus 30-min?

Use 30-min for product builds. Use 15-min automation audits when ops workflows are the main topic.

Can multiple stakeholders join?

Yes—prefer one decision-maker plus the person who knows the workflows.

What if I only have an idea napkin?

Still useful. We will help turn it into a v1 job statement and a band.

Do you record the call?

Only with consent. Notes are the default artifact.

What languages can we use?

English by default; tell us if bilingual facilitation helps your stakeholders.

Sample questions we may ask you

Who is the primary user and what job are they hiring the app to do in the first thirty days? What happens today without the app—spreadsheets, WhatsApp threads, paper?

Which platforms are non-negotiable on day one and why? Who will maintain the app after launch—internal hires, us on retainer, or undecided?

Which systems must connect in v1 versus later? What data is sensitive, and who is your compliance owner if any?

What date is real versus aspirational? What happens if you miss it—lost event, lost funding narrative, or mild inconvenience?

Sample questions you should ask us

Which case studies are closest to our problem, and what would you do differently now? How do you handle change orders when roles expand mid-build?

Who are the named owners on weekly demos? What does handover include—docs, CI, store process, crash tooling?

When do you recommend no-code or delay? How do Miami visits work if our stakeholders are remote-first?

Red flags in any vendor consultation (including us)

Guaranteed rankings, invented download metrics, or Band A quotes for obvious multi-role compliance systems. Pressure to sign before a written SOW. Refusal to discuss assumptions.

If we ever sound like that, call it out. The consultation exists to reduce ambiguity, not to manufacture false certainty.

Turning notes into a SOW

After the call, we summarize band, risks, and open questions. You confirm or correct. Then we draft milestones, exclusions, and commercial terms.

SOW quality correlates with preparation quality. Napkin ideas can start a call; they cannot finish a contract without decisions.

If you need procurement language or security questionnaires, send them early so legal review does not surprise the launch calendar.

Minute-by-minute example (illustrative)

Minutes 0–2: introductions and goal of the call. Minutes 2–7: primary user and current workaround. Minutes 7–18: screens and integrations on a shared outline—not pixel design. Minutes 18–25: risks, compliance, hiring. Minutes 25–30: band orientation and next artifacts.

If you arrive with a Figma already, we still start with the user job. Pretty screens attached to the wrong job waste money faster than blank canvases.

If you arrive with only a napkin, we spend more time on Phase 0 language so the band means something. Either starting point is valid; the agenda adapts.

Materials that accelerate a good call

• Five competitor or inspiration links with notes on what to copy and what to avoid
• A rough user journey in bullets (even unfinished)
• API docs or CRM field lists if integrations are central
• Any compliance questionnaire already required by your buyers
• Decision deadlines tied to real events

Do not delay booking until the packet is perfect. Book, then send materials in the Calendly notes or a follow-up email without secrets.

Commercial clarity without pressure

We explain locked bands early so nobody is surprised later. Soft orientation is not a binding quote. Binding numbers arrive in a SOW after assumptions are confirmed.

Payment milestones usually track demos and deliveries, not calendar vibes. Maintenance is quoted separately when you want ongoing ownership help.

If budget is capped below the honest band for your scope, we discuss cutting roles or platforms—not pretending the same scope fits a smaller band.

Remote versus in-person consultations

Most consultations are remote with screen share. In-person at 7969 NW 2nd Street helps when multiple stakeholders need a whiteboard and the product spans ops plus customer experience.

Hybrid works: Miami team in the room, remote finance on Zoom, same agenda. Send the outline beforehand so nobody spends ten minutes finding the right deck.

After you receive the summary

Reply with corrections within a few business days while context is fresh. Silence makes SOWs guess. If priorities changed, say which must-haves died.

When you approve the summary direction, we draft the SOW. Legal review time belongs on your calendar as much as ours.

If you choose another vendor, the summary still helps you evaluate them. Clarity travels.

Booking logistics

Use the shared closer on this page to open Calendly for a 30-minute product scoping call. Choose 15 minutes only when the topic is automation ops rather than a full product build.

Include time zone and stakeholder names in the invite. If a translator or bilingual facilitation helps, say so in the notes so we staff accordingly.

Reschedule early if decision-makers cannot attend. A call without a decision-maker usually produces a second call.

What success looks like after the consultation

Success is shared clarity: a band, a risk list, and agreed next artifacts. It is not a signed contract on the same day unless discovery was already complete before the call.

If you leave more confused than you arrived, tell us. We will schedule a focused follow-up on the open questions rather than forcing a premature SOW.

Keep the summary with your internal stakeholders. Alignment inside your company is often the longest pole—not the vendor call itself.