Question 1

What types of software does The ScaleUp build?

Accepted Answer

We build mobile apps for iOS and Android, desktop applications for Windows, macOS and Linux, websites and web applications, enterprise and custom business systems, cloud infrastructure, and AI-powered automation. Our UI/UX designers and QA engineers work alongside developers on every project.

Question 2

How much does a software project cost?

Accepted Answer

Cost depends on scope, platforms, integrations and timeline. After a short discovery phase we provide a detailed estimate with a budget range, so you can compare options and decide. Use the quote form to start the conversation.

Question 3

How long does it take to build a product?

Accepted Answer

A focused first version of a website usually takes four to eight weeks. Mobile and desktop apps commonly take three to six months. Larger platforms are delivered in phases so you see value early.

Question 4

Do we own the source code?

Accepted Answer

Yes. You own the code, designs and documentation we create for you, and you have access to the repositories and infrastructure throughout the project.

Question 5

Will you sign an NDA?

Accepted Answer

Of course. We are happy to sign a mutual NDA before you share details about your idea or business.

Question 6

Do you work with startups or only established companies?

Accepted Answer

Both. We help founders turn ideas into a first release and help established companies modernize and extend the systems they depend on.

Question 7

How do we communicate during the project?

Accepted Answer

You get a shared channel, a weekly status update and a demo every sprint. A named project lead is your single point of contact.

Question 8

What happens after launch?

Accepted Answer

We offer support plans that cover monitoring, bug fixes, updates and new features, so your product keeps improving after it goes live.

Question 9

Should we build native or cross-platform?

Accepted Answer

If the app relies on heavy graphics, advanced device features or the newest platform capabilities, native is usually the better choice. For most business apps, cross-platform gets you to market faster with one codebase. We recommend based on your product, not on what we prefer.

Question 10

How long does a mobile app take to build?

Accepted Answer

A focused first version typically takes three to five months, depending on scope. We agree on a prioritized feature list in the first weeks so you can see a working build early and adjust as you learn.

Question 11

Can you take over an app that another team started?

Accepted Answer

Yes. We start with a code and architecture review, tell you honestly what is worth keeping, and then either continue the build or plan a staged rewrite.

Question 12

Why choose a desktop app instead of a web app?

Accepted Answer

Desktop apps shine when you need offline use, direct hardware access, high performance on large data, or tight control over deployment. If none of those apply, a web app is often simpler to maintain.

Question 13

Can one codebase run on Windows, macOS and Linux?

Accepted Answer

Yes, with frameworks like Tauri, Electron and Qt. We help you weigh the trade-offs in size, speed and native feel before choosing.

Question 14

Do you handle code signing and installers?

Accepted Answer

Yes. We set up code signing, notarization for macOS, installer packages and an update channel as part of the project.

Question 15

Will the website be optimized for search engines?

Accepted Answer

Yes. Every site we build ships with semantic markup, metadata, structured data, a sitemap, fast loading and clean URL structure. Content strategy and ongoing SEO work can be added as a separate engagement.

Question 16

Can we edit content ourselves?

Accepted Answer

Yes. We connect the site to a headless CMS or build a simple admin area so your team can publish pages and posts without code changes.

Question 17

Do you build and host the full stack?

Accepted Answer

We handle front end, back end, database, APIs and deployment. We can host on the cloud of your choice and set up monitoring and backups.

Question 18

When does custom software make more sense than a packaged product?

Accepted Answer

When your process is a competitive advantage, when you are paying for features you do not use, or when you spend significant time moving data between tools by hand. We will tell you if an existing product would serve you better.

Question 19

Can you modernize a system we already depend on?

Accepted Answer

Yes. We map what the system does today, move it in stages and run old and new side by side until the new one is proven.

Question 20

Who owns the code?

Accepted Answer

You do. Source code, documentation and infrastructure access are yours at every milestone.

Question 21

Which cloud provider should we choose?

Accepted Answer

The one that fits your team, your existing contracts and your compliance needs. We work across all three major providers and avoid lock-in where it is not worth the cost.

Question 22

Can you help reduce our cloud bill?

Accepted Answer

Yes. A cost review usually finds quick wins in unused resources, oversized instances and storage tiers, followed by longer-term architecture improvements.

Question 23

Do you offer on-call and managed operations?

Accepted Answer

We offer monitoring and support plans with agreed response times. See our engagement models for details.

Question 24

Can you design only, without development?

Accepted Answer

Yes. We hand over production-ready designs, specifications and a component library your in-house or other development team can implement.

Question 25

How do you work with our developers?

Accepted Answer

Designers and engineers collaborate in the same sprint. Designs are reviewed for feasibility early, and we review the built result against the design before release.

Question 26

Do you test designs with real users?

Accepted Answer

Yes. We recommend at least one round of testing with five to eight representative users before development begins.

Question 27

Is our data safe when we use AI features?

Accepted Answer

We design data flows so sensitive information stays within your agreed boundaries, choose providers with appropriate data terms and add logging and access controls. We review requirements with your security team early.

Question 28

How do you keep AI answers accurate?

Accepted Answer

We ground answers in your approved content, measure quality against a test set and route low-confidence cases to a person.

Question 29

Where should we start with AI?

Accepted Answer

Pick one repetitive, well-defined process with clear volume. A short discovery workshop identifies the best candidates and what each would save.

Question 30

Can you support software you did not build?

Accepted Answer

Yes. We begin with a review of the codebase and infrastructure, document how it works, and then agree on a support plan.

Question 31

What response times do you offer?

Accepted Answer

Plans define response targets by severity. Critical production issues receive the fastest response. Details are set out in your support agreement.

Question 32

How is support priced?

Accepted Answer

Usually as a monthly retainer for an agreed amount of capacity, so you can rely on it without managing hourly invoices.

Answers to common questions

General

Mobile app development

Desktop app development

Website and web app development

Custom and enterprise software

Cloud and DevOps

UI/UX design

AI and automation

QA, maintenance and support

Still have a question?