Your business, running on its own agents.
Miqromanage is the full Miqro Inc offering — a dedicated Railway
project, a dedicated agent stack, a subdomain on
miqromanage.app (custom domain optional), and a live
dashboard. We run the infrastructure; you stay in the driver's seat
via approvals. Specific scope, price, and behavior live in your
signed contract.
What a typical engagement includes
Tier 1 and Tier 2 share Miqro Inc infrastructure. Miqromanage engagements are scoped per-tenant. The list below is illustrative — the specific surfaces, agents, and integrations included in your build are written into your signed contract.
Dedicated Railway project
A project under miqromanage-<your-business>. Your agents and logs run there; deploys are visible to you.
Subdomain on day one
<your-business>.miqromanage.app ships with
SSL. A custom domain can be migrated afterwards via your DNS
provider; specific vendors and timing are scoped in the
proposal.
Configured agent stack
Agents typically wired for the engagement: prospecting, scoring, email, SMS, voice, design, reporting. The exact roster and configuration is set in your contract — third-party model and integration availability affects behavior.
Tenant-scoped data
Your leads, outreach history, and metrics are scoped to your tenant in our database. Cross-tenant access is restricted by the same row-level isolation we use internally.
Live dashboard
A customer portal at miqromanage.app typically surfaces agent activity, site performance signals, and recent lead touches. Specific dashboard surfaces evolve; the contract names which views are committed.
Recurring reports
A weekly email summary covering leads discovered, outreach sent, calls placed, and bookings. Cadence and contents are confirmed in your contract.
Analytics & insights suite
The sites we run carry a single cookieless beacon — no consent banner, no PII — feeding web analytics, click heatmaps, A/B tests, and on-site surveys into your dashboard. One script instead of a stack of separate analytics, heatmap, and survey subscriptions. Scope is set in your contract.
Support desk for your site
The same agents that operate your site triage issues raised about it and draft replies for your approval — support for what we built and run, rather than a separate help-desk product bolted on. Coverage, response targets, and any human escalation path are written into your retainer.
How an engagement runs
Nothing is signed and no money moves until we meet to review the contract together. See Terms §6–§7 for the binding workflow.
Submit intake
Six minutes of questions about your business. We review.
Quote drafted from your intake
We email an exploratory proposal with estimated price, target timeline, and a draft contract. It's an estimate, not an offer.
Contract review meeting
We walk through the proposal and the draft contract together (video or in person). Nothing is signed before this meeting.
Signed contract + deposit
At or after the review meeting, both sides sign and the deposit invoice is paid. This is the binding step.
Provision + launch
We provision your Railway project, subdomain, database scope, and agent stack against the contracted scope; the launch call walks you through it.
Ongoing ops
Weekly reporter email; ongoing support per your retainer terms.
Pricing
Estimated ranges. Tier 3 is scoped per engagement — onboarding plus a monthly operations fee. Final scope and binding price are written into your signed proposal after the contract-review meeting. Ranges below are not quotes.
Operations layer
- Dedicated Railway project
- Dedicated subdomain + SSL
- Agent stack typically wired for prospecting, outreach, voice, reporting
- Cookieless analytics, heatmaps, A/B testing & surveys in your dashboard
- Support desk — agents triage & draft replies to issues on your site
- CRM migration where compatible with your current system
- Multi-location console where applicable
- Weekly ops reports
- Support response targets are written into your retainer
Common questions
Do I have to use miqromanage.app?
No. It's your starting subdomain so you have SSL on day one. Custom-domain migration is scoped in the proposal; the timing and DNS path are written into the contract.
Can I see the code?
Yes — your engagement's Railway project is visible to you during the engagement so deploys are auditable. Specific access scopes are confirmed in the contract.
What happens if I cancel?
Cancellation terms (notice period, data export, Railway project transfer, access removal) are written into your retainer contract. The default is 30 days notice; the binding terms are in your signed agreement.
Do my agents see other customers' data?
Your agents read from your tenant-scoped Supabase data only. Our control plane handles billing and provisioning, not your business data. Specific data-handling guarantees are written into the data-processing addendum in your contract.
Ready to scope an engagement?
Start the intake. We draft an exploratory quote within two business days and book a contract-review meeting from there. Nothing is signed before the meeting.