Do you work fixed scope or retainer?

Both. We recommend fixed scope for a defined MVP, then a monthly retainer for growth, maintenance, and experiments.

What do projects typically cost?

Discovery/MVPs often start in the ₦3.5m–₦9m range; larger platforms vary by scope, integrations, and SLAs. We’ll price after a short scoping call.

How do payments work?

50% to kick off, 30% at mid-milestone, 20% at handover. Retainers are billed monthly in advance. Invoices via DevPayr/Paystack/Stripe.

How fast can we get a first version live?

Usually 4–6 weeks for an MVP. We ship a first working slice early, then iterate weekly.

How do we communicate during the project?

Weekly demos, shared Slack/Notion for updates and decisions, GitHub for code and issues.

Can you work with our existing codebase or designs?

Yes. We run a quick audit, confirm risks, then continue if the foundation is sound. If not, we suggest a stabilization plan.

Which technologies do you use?

Laravel, Node/Nest, Vue/React, Flutter, PostgreSQL, Redis, Docker, with CI/CD, telemetry, and security by default.

Will the product scale as we grow?

Yes. We plan for caching, queues, observability and horizontal scaling. Hot paths get budgeted p95 targets.

How do you handle security?

RBAC, MFA, rate limits, audit logs, secure secrets, dependency checks, and periodic reviews baked in.

Do you support compliance needs?

We align to your policies (PII, data-retention, backups). If formal audits are needed, we coordinate with your compliance team.

Can you integrate payments and logistics?

Yes—Paystack, Flutterwave, Stripe, Nomba, plus dispatch/logistics, CRMs, ERPs, and analytics.

Do you build multi-tenant SaaS?

Yes. We handle tenant isolation, billing/proration, webhooks, and usage metering.

Who owns the code and IP?

You do. Repos transfer at handover. We only keep our internal boilerplates and utilities.

Will you sign an NDA and DPA if required?

Yes. We have standard templates, or we can review and sign yours.

Do you provide post-launch support?

Yes—support tiers include monitoring, patching, incident response, and small improvements.

What happens if there’s an incident?

We run an on-call playbook with clear SLOs, status comms, and a post-mortem. Prevention via observability is the baseline.

Can you migrate our data?

Yes. We agree on mapping, run dry-runs, verify totals, and cut over with a back-out plan.

Kickoff slots open monthly. After a 30-min discovery call, we lock dates and team.

FAQs

Answers that make decisions easy.

Buying, timelines, security, and support — the essentials, no fluff.

Start a Project Book a Discovery Call Updated Jan 14, 2026

Pricing depends on scope, integrations, and SLAs. We’ll scope with you first, then price.

faqs.xultech.io

Buying Process Tech Security Integrations Legal Support Data Timeline

Clear policies. Fast responses. Practical guidance. No jargon.

of answers

Updated Jan 14, 2026

Ready to move from questions to clear scope and a calm launch?

Tell us your goals. We’ll help define scope, risks, and success metrics—then ship with security, telemetry, and clean handover. Pricing always depends on scope, integrations, and SLAs.

Start a project Book a discovery call

99.9% uptime

p95 < 300ms core paths

Clear handover CI/CD + docs

Founder-led delivery

Security Assessment

DevPayr

See our results

Answers that make decisions easy.

Ready to move from questions to clear scope and a calm launch?