Question 1

What does maykaTech actually do?

Accepted Answer

We design, build, and operate custom software for mid-market and enterprise companies: web and mobile products, cloud platforms, AI systems, and the modernization of legacy systems businesses depend on. Teams of 4–9 engineers and designers take products from discovery through production and, for most clients, keep improving them for years afterward.

Question 2

How much does a typical project cost?

Accepted Answer

There's no rate card — every engagement is scoped individually, because a compliance-heavy platform and a marketing site have nothing in common except a keyboard. After discovery you get a written proposal with the reasoning behind the number, and during delivery we publish weekly burn reports so spend is never a surprise. We'll also tell you in the first call if your budget and scope don't match, before either of us spends more time.

Question 3

How long does it take to build a custom product?

Accepted Answer

A focused v1 typically reaches production in 3–5 months, with working software demoed every two weeks from the start. Complex integrations, compliance requirements, or migration work extend that — and we'll give you an honest range, not the optimistic one, during discovery.

Question 4

Do you work with startups or only enterprises?

Accepted Answer

Both, with a caveat for early startups: we're a strong fit once you have validated demand and funding for a real build (typically seed stage onward). Pre-validation, you usually need experiments, not engineering — and we'll say so rather than take the money.

Question 5

Where is your team located?

Accepted Answer

Headquarters in San Francisco with delivery centers in Austin, London, and Bengaluru — about 180 people total, all employees rather than contractors. Client teams are staffed for at least four hours of working-time overlap with your core hours, whatever your timezone.

Question 6

Who owns the code you write?

Accepted Answer

You do, entirely and from day one: source code, infrastructure configuration, design files, and documentation, under a standard work-for-hire agreement. There is no license-back clause, no proprietary framework dependency, and no hostage scenario if we part ways.

Question 7

Can you take over a project from another team?

Accepted Answer

Yes — inherited codebases are roughly a third of our new engagements. We start with a two-week technical audit that maps risks, documents what exists, and produces a stabilization plan. We're careful about not disparaging previous teams; most troubled projects are the result of constraints, not incompetence.

Question 8

How do you handle security and compliance?

Accepted Answer

maykaTech is SOC 2 Type II audited annually. We build routinely under HIPAA, PCI DSS, and GDPR constraints, sign BAAs where required, and bake compliance into architecture — encryption, least-privilege access, and audit logging from the first commit rather than a remediation sprint before launch.

Question 9

What happens after launch?

Accepted Answer

Whatever you choose: full handover to your team with documentation and pairing, a managed support plan with 24/7 monitoring and SLAs, or a standing product squad that keeps shipping improvements. About 94% of clients continue with us in some form after the first release — retention we consider our most honest metric.

Question 10

Why shouldn't we just hire our own engineers instead?

Accepted Answer

Long-term, you probably should — and we'll help you do it. A hiring pipeline takes 6–12 months to produce a productive team; we're how the product ships in the meantime. Many engagements end with us onboarding your new hires into a codebase they'll be glad to inherit, and we consider that a success, not lost revenue.

The questions everyone asks. Answered like we mean it.

Still curious about something?

Tell us what's slowing your business down