Everything you need, before and after you go live.

It is the single input to your deployment. You describe your users, your service workflow, your pricing model, your compliance needs, and the outcomes you want — in plain language. TempoDyn's infrastructure engine reads that and provisions your databases, workflows, AI agents, authentication, payments, analytics, and compliance layer.

There is no separate spec, no discovery phase, and no custom engineering. The form is the spec. Start it at enterprise-onboarding.

Gather these first — they are the answers the intake is built around:

Specific enough that someone outside your industry could build it. Compare:

Too vague — “We're a healthcare marketplace.”

Right — “We connect patients seeking second opinions with vetted specialists. We need HIPAA compliance, payments, video consults, and AI matching.” That single sentence produces a patient intake agent, a specialist matching engine, a HIPAA audit vault, payment escrow, and an outcome feedback loop.

Name your user types, your steps, your edge cases, and the systems you already run. Vague inputs produce a generic platform; precise inputs produce yours.

Start with the Pilot regardless. Every paid plan begins with the same free 30-day pilot, and no credit card is required. Selecting Growth, Scale, or Enterprise on the form simply tells us which tier to configure toward — it does not bill you.

If you are a regulated enterprise needing a BAA/DPA, on-premises inference, or procurement support, choose Enterprise so the right team is assigned from the start.

No. The pilot is designed to launch without ripping out existing systems. CRM and EHR integrations are part of what TempoDyn deploys, but they are not a prerequisite for going live. Name the systems you run in the intake, and integration is planned around your first workflow rather than blocking it.

Your platform is provisioned and you receive admin credentials and your server IP address. From there, follow the deployment and admin configuration sections below. Typical time from submitted form to a working platform is under 24 hours.

Co-Founder Program applications are reviewed within 48 hours.

Create a DNS A record pointing your fully qualified domain name at the server IPv4 address TempoDyn provided. Do this first — every other setup step assumes the platform is reachable.

1. Sign in to your DNS management console (Route 53, Windows DNS Manager, Infoblox, your registrar — whatever your organisation uses).
2. Open the DNS zone matching your domain — open yourcompany.com to add app.yourcompany.com.
3. Choose Add record and select record type A (Address).
4. Fill in the fields (see the next question), then Save.
5. Confirm the record appears in the zone list with the right name and IP.

Open a terminal and query your default resolver:

In the ANSWER SECTION, confirm the name matches your FQDN, the type is A, and the address is the server IP you were given.

Then compare against a public resolver to confirm propagation:

Both should return the same IP once propagation completes.

• Confirm the record exists in the correct zone and the name is spelled correctly.
• Confirm you're querying the resolver you think you are — corporate resolvers and public resolvers can disagree during propagation.
• Cached records persist until the TTL expires. Wait out the TTL or flush your local DNS cache if policy allows.
• If several A records exist for the same name (round-robin or load-balanced), dig lists them all — confirm the new IP is among them.

To trace the full resolution path from root to your authoritative servers:

Yes — deployment itself typically completes in under 60 minutes, and the 24-hour window covers the full path from your description to a working pilot with your first workflow, users, and success metric in place. Healing Tourist, a live HIPAA-compliant healthcare marketplace, was deployed on this timeline with zero custom engineering.

The part that can add time is on your side: DNS propagation, and getting your team's invitations out.

Sign in with your Enterprise Admin credentials in the latest Chrome or Edge, then confirm:

• You land on the dashboard, with the left navigation, greeting, and quick prompts visible.
• The chat input area is present — text field, microphone, and send button.
• Every item in the left navigation opens without error.

If any menu fails to open, resolve it before configuring anything else.

Open Settings and confirm the sign-in URLs open correctly and point at your production environment — not a staging link. Then make a small change, save it, and refresh to confirm it persists. Finally, confirm admin-only settings are not visible or editable to non-admin roles.

Open Invitations. Two roles matter:

• Member — your general team, working in the admin/user side.
• Expert — providers and clinicians who use the Expert portal.

Enter the email, choose the role, select the invitation type, and send. Use a real address you control for at least one invite so you can walk the sign-up flow end to end.

You can resend an invitation email, copy the link, or cancel an invite — cancelling should immediately invalidate the link.

Go to Team Admin › Members. As people accept invitations they appear here. Confirm every member is present with the correct role, and that search returns accurate results.

Removing a member requires a confirmation step, so it can't happen by accident.

Open the Doctors tab. Review pending approvals and approve the providers who belong to your organisation. Then confirm they appear in the roster with the correct specialties, and open a profile to check the details.

Open AI Agents. Toggle each integration on or off, and confirm the list reloads cleanly on refresh. Use Create Custom Agent if your workflow needs one that isn't in the default set.

Enable only the agents you need at launch — you can add more at any time. Give custom agents a clear name and description so your team understands what each one does.

Agent limits depend on your plan: 10 on Pilot, up to 100 on Growth, unlimited on Scale and Enterprise. Scale and Enterprise also include the Agent SDK so your own team can build agents.

Open Support. Incoming requests from guests and users land here, segmented by New, Read, and Archive filters. Each message shows sender details and a timestamp; you can mark read and archive.

Before go-live, decide who on your team monitors this queue.

Run this end-to-end pass. Every row must pass before you announce the platform to your users:

1. Log in as Enterprise Admin — dashboard loads cleanly.
2. Review the dashboard — navigation and chat input present.
3. Invite a new expert — invitation email is received.
4. Approve the expert — approval completes.
5. Check the roster — the expert now appears.
6. Open AI Agents — agents load and toggle.
7. Submit a guest support request — it appears in Support.
8. Navigate across all modules — no errors anywhere.
9. Log out and back in — your changes persist.

Most platforms are static — they do exactly what someone built them to do. TempoDyn platforms improve their own matching and routing by learning from what actually happened: which match worked, which route resolved, which intake led to a good outcome. That learning is federated, meaning it happens without pooling raw data from your environment or anyone else's. Your platform gets smarter; your sensitive data stays put.

No. Tenant data is isolated and there is no raw data pooling. This is a property of the architecture, not a promise in a contract — the system is built so that raw records have nowhere to go. That is what makes federated learning viable in regulated environments like healthcare, financial services, and government.

You don't. Your agents inherit behavioural intelligence from prior deployments in your category before your first user signs up — roughly 18 months of accumulated industry learning on day one. The Vertical Intelligence Index shows how deep your industry's intelligence already is, before you deploy.

A competitor building from scratch spends those 18 months catching up to where you started.

No configuration required. Federated learning is active automatically on Growth, Scale, and Enterprise. The platform improves nightly from service interactions with no engineering effort from your team.

On the free Pilot you get the Vertical Intelligence Index baseline, but active federated learning starts at Growth.

Scale and Enterprise add advanced FL controls and explainability — so you can see why the model is routing the way it is. Enterprise adds custom federated model development.

A typical trajectory: by month six the platform has processed 10,000+ interactions with matching accuracy above 70%. By month twelve the model has updated roughly 52 times — once a week — with accuracy above 85%. Healing Tourist runs at 94% AI matching accuracy across 2M+ patients matched.

Your figures depend on volume and workflow. Your Solutions Engineer reviews them with you at each QBR (Scale and Enterprise).

No. The 30-day pilot is free with no card required. You describe your business, we deploy your platform, and you test it with real users. At day 31 you choose a paid plan or stop — there is no auto-billing.

An AI agent is any intelligent workflow component that operates autonomously — a patient intake agent, a specialist matching engine, a compliance monitoring agent, a payout automation agent. Each handles one specific function inside your platform.

Pilot: 10 agents. Growth: up to 100. Scale and Enterprise: unlimited.

Growth ($499/mo) fits most funded startups: 5,000 users, 100 agents, full compliance stack, federated learning active.

Scale ($1,499/mo) adds unlimited agents, multi-region deployment, a dedicated Solutions Engineer, a 99.95% SLA, advanced FL controls, and the Agent SDK. Choose Scale when you operate in multiple geographies, need more than 100 agents, or want a dedicated technical partner.

Full plan details are on the pricing page.

HIPAA and GDPR compliance architecture is included in every plan from day one, including the free Pilot. Additional modules — FINRA/SEC, ISO 27001, SOC 2 Type II reports, DPDP Act — are available as add-ons, or included in Enterprise. The FINRA/SEC compliance module is $200/month on Growth and Scale.

BAA and DPA agreements are included from Scale upward.

Paying annually saves 17% — about two months free. Growth: $4,990/year versus $5,988 billed monthly. Scale: $14,990/year versus $17,988 monthly. Annual invoices are issued upfront. Enterprise is negotiated as an annual contract regardless of payment frequency, with a $60,000/year minimum.

Yes. Upgrades take effect immediately; downgrades take effect at the next billing cycle. If you outgrow your tier, your Solutions Engineer will flag it at your QBR — there's no lock-in pressure, and you can cancel at any time.

No monthly fee, plus:

• Complete infrastructure-as-code platform deployment
• TempoDyn listed as Technical Co-Founder
• Dedicated Solutions Engineer for 12 months
• Unlimited AI agents for 12 months
• Continuous federated learning, active
• Full compliance stack from day one
• Public case study and milestone press releases
• Investor network introductions
• Featured on the 0-to-Platform demo show
• Vertical Intelligence Index priority access

The Co-Founder Program replaces the monthly fee with an equity stake of 1–3% depending on stage. You get Scale-tier features — dedicated SE, unlimited agents, federated learning — plus investor network access, at zero cash cost.

It's built for pre-seed and seed founders where cash is the constraint and speed is the advantage. If you're funded and want to keep your cap table clean, take Growth or Scale instead — see pricing.

Apply online at the Co-Founder application.

Applications are reviewed within 48 hours. Equity terms are finalised after acceptance, and there are no legal fees to apply.

Ten spots open each quarter. Include your stage, your vertical, your traction, and the workflow you want deployed.

Open Settings and verify every environment URL points at production — not staging. Fix and save before resending invitations. Broken invite links almost always come from URLs configured out of order.

• Confirm the A record is in the correct zone and the hostname spelling matches your FQDN.
• Compare dig results from your default resolver and a public resolver (8.8.8.8).
• Wait out the TTL, or flush local DNS cache if policy allows.
• If round-robin A records exist, confirm the TempoDyn IP is among them.

More detail is in the deployment section above.

Use the latest Chrome or Edge. Confirm you are signed in as Enterprise Admin. If one nav item fails, resolve it before inviting more users — a broken module during onboarding usually surfaces as cascading support tickets later.

Email solutions@tempodyn.com with the module name, the action you took, and the exact error message. That detail is usually enough to resolve on the first reply.