Question 1

Where is XiteHub based?

Accepted Answer

The studio is in Karachi, Pakistan. Founded in 2021. We have delivered 80+ products for teams in more than 10 countries.

Question 2

How do I get started?

Accepted Answer

Book a 30-minute Calendly slot or send the consultation form. A solutions architect sends a written next step within 48 hours.

Question 3

Who owns the source code?

Accepted Answer

You do. Repositories, cloud accounts, and third-party licenses sit in your name. We keep access only while you hire us to maintain the system.

Question 4

Do you work outside Karachi?

Accepted Answer

Remote is decided per brief, not as a slogan. The company is based in Karachi. We do not list delivery centers we do not run.

Question 5

What engagement models do you offer?

Accepted Answer

Fixed scope after discovery when the edges are clear. A dedicated team when the backlog will keep moving. A monthly retainer when you want the same people after launch.

Question 6

Do you stay after launch?

Accepted Answer

Yes. The same people who built it stay for the first weeks of production. Ongoing maintenance is scoped separately. We do not sell a 24/7 stamp we cannot staff.

Question 7

Are these fixed prices?

Accepted Answer

No. The figures on this page are starting estimates from typical team size and timeline. The quote after discovery is the one that binds.

Question 8

Can I hire just one role?

Accepted Answer

Yes. Any role can be monthly or hourly. Many briefs start with one frontend or one backend and add people when the work needs them.

Question 9

What if nothing on the list matches?

Accepted Answer

Book a consultation. We will name the mix for the brief, for example two backends and one frontend for an API-heavy platform, or a designer only before build.

Question 10

Do you lock a fixed price?

Accepted Answer

Yes, after discovery, when scope and milestones are clear. That is common for sites and MVPs with a defined first slice.

Question 11

What currency are the figures in?

Accepted Answer

Starting estimates are in USD. Billing currency and schedule are confirmed on the written quote.

Question 12

When is custom software the right call instead of buying a product?

Accepted Answer

When your process is the product, or when packaged tools force workarounds that cost more than a build. We will say so if a Shopify app, an ERP module, or a no-code tool already covers the job.

Question 13

Who owns the source code?

Accepted Answer

You do. Repositories, cloud accounts, and third-party licenses sit in your name. We keep access only for the period you hire us to maintain the system.

Question 14

Can you replace a system our last vendor left undocumented?

Accepted Answer

Yes. We inventory screens, data, and integrations first, then migrate in phases so you are not cut over in a single weekend.

Question 15

How do you price a custom build?

Accepted Answer

Fixed scope after discovery when the edges are clear. A dedicated team when the backlog will keep moving. We estimate after we have seen the workflows, not from a one-page brief.

Question 16

Will this replace our ERP?

Accepted Answer

Not by default. Most clients keep SAP, NetSuite, or a regional ERP and ask us for the workflow layer those products handle poorly. We integrate rather than force a rip-and-replace.

Question 17

How do you handle downtime during go-live?

Accepted Answer

We prefer dual-running and batch cutovers by site or business unit. A weekend freeze is a last resort and only when both sides have a written rollback.

Question 18

Can your team sit with our internal engineers?

Accepted Answer

Yes. We join existing standups, ticket boards, and review rules. Dedicated XiteHub squads are available when you want a self-contained workstream.

Question 19

What compliance artifacts do you produce?

Accepted Answer

Access matrices, data-flow notes, and change records that your auditor can read. We align to the controls you already follow, such as SOC 2 or GDPR, rather than inventing a parallel program.

Question 20

How long does a first paid version take?

Accepted Answer

A focused MVP with auth, one core workflow, and Stripe is often 8 to 14 weeks after discovery. A marketplace or a product with several roles takes longer. We date the first invoice, not a slide deck.

Question 21

Should we start multi-tenant or single-tenant?

Accepted Answer

Most B2B SaaS should start with logical multi-tenancy and strong isolation. Single-tenant or VPC deploy is a later SKU when a buyer’s security review demands it.

Question 22

Do you handle subscription tax and invoicing?

Accepted Answer

We implement Stripe Billing, customer portals, and the webhooks that keep entitlements in sync. Tax registration and accounting remain yours or your bookkeeper’s.

Question 23

What happens after launch?

Accepted Answer

A retainer or a smaller squad for roadmap work is typical. The same repo and the same engineers stay on the product so you are not briefing a new team every quarter.

Question 24

Can marketing publish without a developer?

Accepted Answer

Yes, if we model the CMS around the pages they actually change. Free-form page builders are possible, but we prefer structured blocks so the site does not decay in six months.

Question 25

Will a redesign kill our search rankings?

Accepted Answer

We map old URLs to new ones and keep indexable content in place. Rankings still move when you change copy or IA, but we do not ship a redesign that 404s the pages Google already knows.

Question 26

Do you build on WordPress?

Accepted Answer

We usually recommend a headless CMS with Next.js for new work. We can take over an existing WordPress site when migration is not yet justified.

Question 27

How do you handle e-commerce?

Accepted Answer

Shopify for catalog and checkout when that is the right store. A custom storefront when checkout, pricing, or B2B rules do not fit a theme.

Question 28

Should we go native or cross-platform?

Accepted Answer

Cross-platform is the default when the app is content, commerce, or operations. We choose native when you need custom camera pipelines, heavy graphics, or OS features that wrappers still fight.

Question 29

What if Apple or Google rejects the first submission?

Accepted Answer

We budget time for review notes. Most first rejections are about permissions copy, login, or payments. We stay on the ticket until the build is live.

Question 30

Can you publish under our developer accounts?

Accepted Answer

Yes. Accounts, signing keys, and store listings stay in your organization. We work as Admin or Developer, not as the owner of your listing.

Question 31

Do you build the API as well?

Accepted Answer

Often yes. Many mobile projects include a Node or Laravel API, admin panel, and the app. We can also consume an API your team already runs.

Question 32

Do we need our own training data?

Accepted Answer

For extraction and ranking, labeled examples from your domain almost always beat a generic model. For generation, a strong base model plus retrieval can be enough. We will not start a training run on empty files.

Question 33

How do you keep costs predictable?

Accepted Answer

We set token or inference budgets, cache repeated calls, and choose smaller models where quality holds. You see unit cost during the pilot, not after the invoice.

Question 34

Can you work with data that cannot leave our VPC?

Accepted Answer

Yes. We can train and serve inside your cloud account with no training data leaving the boundary you set.

Question 35

What if AI is the wrong tool?

Accepted Answer

We stop. A scoring rule, a search index, or a better form often beats a model. You pay for the assessment, not a forced AI feature.

Question 36

How is this different from a chatbot?

Accepted Answer

A chatbot answers. An agent acts: it calls tools, updates records, and moves a workflow forward. If you only need answers from a knowledge base, we will recommend a chatbot or RAG instead.

Question 37

What stops an agent from doing something harmful?

Accepted Answer

Scoped credentials, allow-lists on tools, spend caps, and mandatory approval on high-risk actions. We do not give an agent a raw production admin key.

Question 38

Do agents replace staff?

Accepted Answer

They take repetitive steps off a queue. Your people still handle exceptions and relationships. We measure time returned to the team, not headcount cut.

Question 39

Can an agent use our existing Zapier or n8n flows?

Accepted Answer

Yes. We often wrap those automations as tools so you do not rebuild every connector from scratch.

Question 40

Will this replace our support team?

Accepted Answer

It should take the repetitive volume: order status, hours, and policy. Agents keep the cases that need judgment. We set a handoff you can see in the same thread.

Question 41

Can the bot take payments or change orders?

Accepted Answer

Only through authenticated APIs and only for actions you approve. We default to read-only plus a human for anything that moves money.

Question 42

Do you support WhatsApp?

Accepted Answer

Yes. We implement WhatsApp Cloud API with message templates that follow Meta’s rules, plus the web widget if you want both.

Question 43

How do you keep answers accurate?

Accepted Answer

The bot reads a curated knowledge source and must refuse when the source is silent. We review failed conversations on a schedule you choose.

Question 44

Is this better than fine-tuning?

Accepted Answer

For company knowledge that changes, yes. Fine-tuning is for style or a narrow task. RAG keeps facts in documents you can update without another training run.

Question 45

Our files are messy PDFs and scans. Will this work?

Accepted Answer

We test extraction first. Clean text and tables work well. Bad scans need OCR and still fail on some layouts. We show you recall numbers before we promise a launch.

Question 46

How do you stop the model from answering from general knowledge?

Accepted Answer

The prompt requires retrieved context. If retrieval is empty, the system says it does not know. We measure that refusal rate on purpose.

Question 47

Can we keep documents inside our cloud?

Accepted Answer

Yes. Embeddings and the vector store can live in your AWS or Azure account. We do not need a copy of the corpus on our laptops after setup.

Question 48

Which process should we automate first?

Accepted Answer

High volume, clear rules, and a painful miss. Invoice matching and lead routing usually beat a once-a-month report. We will walk a week of tickets with you before we pick.

Question 49

What if our systems have no API?

Accepted Answer

We look for exports, IMAP, or a vendor API we missed. Screen automation is last and only for stable UIs. We tell you the maintenance cost before we go that route.

Question 50

Will staff lose their jobs?

Accepted Answer

Our brief is to give hours back to the same team. Headcount decisions are yours. We design exception queues so people still handle the cases software should not touch.

Question 51

Can you take over automations a former employee built?

Accepted Answer

Yes. We document, add logging, and move them into a shared workspace so the next person is not guessing.

Question 52

Is this a lift-and-shift?

Accepted Answer

Only when the goal is to leave a data center quickly. We will say when a service should be rewritten or replaced with a managed database instead of copied as-is.

Question 53

Do we need more than one cloud?

Accepted Answer

Usually no. Multi-cloud is a product of acquisitions or a hard vendor requirement. We default to one well-run account.

Question 54

Will our bill go up after migration?

Accepted Answer

It can, if you copy every VM. We show a forecast before cutover and a second pass after 30 days of real traffic.

Question 55

Can you work with our existing MSP?

Accepted Answer

Yes. We take architecture and migration, they keep tickets, or the reverse. We will not fight over who owns IAM without a written split.

Question 56

We already have Jenkins. Do we have to move?

Accepted Answer

No. We will stabilize Jenkins if that is cheaper than a migration. A move to GitHub Actions or GitLab is a recommendation, not a condition.

Question 57

What is GitOps in your work?

Accepted Answer

Desired state in git, a reconciler such as Argo CD, and no hotfixes applied only in the cluster. We use it when you have more than a handful of services.

Question 58

Do you provide on-call?

Accepted Answer

On a support retainer, yes, within the hours in the order. Day-to-day DevOps engagements are about making your team able to run the night, not taking the pager forever.

Question 59

Can you set this up for a two-person startup?

Accepted Answer

Yes, with a smaller footprint: one pipeline, two environments, and basic alerts. We will not sell you a platform team’s stack.

Question 60

Should everything be automated?

Accepted Answer

No. Automate the paths you run every sprint and the ones that have bitten you twice. Exploratory testing stays on new UX and messy integrations.

Question 61

Can QA sit inside our sprints?

Accepted Answer

Yes. We join refinement, write cases while the story is in progress, and block merge when the risk says so. A late test-only phase is the fallback, not the default.

Question 62

Do you do penetration testing?

Accepted Answer

We run DAST and a structured security test pass. A formal pentest with a certified firm is something we can coordinate, not something we pretend to stamp ourselves.

Question 63

What about apps on real phones?

Accepted Answer

We use device clouds and a small physical set for the OS versions your analytics show. We will not claim we tested every Android skin.

Question 64

Can you design without building the product?

Accepted Answer

Yes. Some clients take a Figma system to an internal team. We still write the handoff as if we will implement it, so the file is not decorative.

Questions, answered

Nine groups, one studio

Go to a category

Studio

Where is XiteHub based?

How do I get started?

Who owns the source code?

Do you work outside Karachi?

What engagement models do you offer?

Do you stay after launch?

Pricing

Are these fixed prices?

Can I hire just one role?

What if nothing on the list matches?

Do you lock a fixed price?

What currency are the figures in?

Development

Custom Software Development

When is custom software the right call instead of buying a product?

Who owns the source code?

Can you replace a system our last vendor left undocumented?

How do you price a custom build?

Enterprise Application Development

Will this replace our ERP?

How do you handle downtime during go-live?

Can your team sit with our internal engineers?

What compliance artifacts do you produce?

SaaS Product Development

How long does a first paid version take?

Should we start multi-tenant or single-tenant?

Do you handle subscription tax and invoicing?

What happens after launch?

Web Development

Can marketing publish without a developer?

Will a redesign kill our search rankings?

Do you build on WordPress?

How do you handle e-commerce?

Mobile App Development

Should we go native or cross-platform?

What if Apple or Google rejects the first submission?

Can you publish under our developer accounts?

Do you build the API as well?

AI & Automation

AI Development

Do we need our own training data?

How do you keep costs predictable?

Can you work with data that cannot leave our VPC?

What if AI is the wrong tool?

AI Agents

How is this different from a chatbot?

What stops an agent from doing something harmful?

Do agents replace staff?

Can an agent use our existing Zapier or n8n flows?

Chatbot Development

Will this replace our support team?

Can the bot take payments or change orders?

Do you support WhatsApp?

How do you keep answers accurate?

RAG Systems

Is this better than fine-tuning?

Our files are messy PDFs and scans. Will this work?

How do you stop the model from answering from general knowledge?

Can we keep documents inside our cloud?

Automation Solutions

Which process should we automate first?

What if our systems have no API?

Will staff lose their jobs?

Can you take over automations a former employee built?

Cloud, Quality & Design

Cloud Solutions

Is this a lift-and-shift?

Do we need more than one cloud?

Will our bill go up after migration?

Can you work with our existing MSP?

DevOps Services

We already have Jenkins. Do we have to move?

What is GitOps in your work?

Do you provide on-call?

Can you set this up for a two-person startup?

QA Testing