GBCORP BLOG · IT SERVICES

An App Developer for My Business: What to Look For, What to Pay

Published August 5, 2022 · 6 min read

You typed app developer for my business because you have a business, and it needs an app. The useful answer is not a name; it is which of three routes fits, what each costs, and what to ask before you pay anyone.

An App Developer for My Business: What to Look For, What to Pay

Most businesses looking for an app developer need one of three things: a branded app that works on day one, a one-time build they own outright, or a custom application built around a process no product covers. GBCORP offers all three, at prices on the e-shop, and the honest first step is deciding which one you are.

The three routes

RouteWhat you getTime to livePricing
Branded white-label appYour brand on a finished app: ordering, booking, loyalty, portalDaysFlat monthly plan
One-time branded buildA configured app delivered once, yours to keepOne to three weeksOne fixed price
Custom applicationBuilt around your process, scoped in a weekEight to twelve weeksFixed price per release

What to ask any developer

Which apps of theirs are in the stores today under their own name. Whether the app will be one codebase for iOS, Android and web, or three budgets. Who will own the code, the cloud project, the domain and the store accounts. What the price is per release, fixed before it starts. What happens when the operating system changes and the app needs an update. Whether they will hand everything over if you want to leave. A developer who answers all six plainly is the one to hire.

What you must own

Your brand, your content and your customer data are yours from the first day. The store developer accounts are opened in your business’s name. The payment-gateway account is yours, so sales settle to you. The domain is yours. On a one-time build or a custom application, the code is yours too. GBCORP writes this into every quotation because it decides whether you have an app or a subscription to someone else’s.

What a business app should contain

Accounts with sign-in that works. The thing your customers do most, on the first screen: order, book, pay, check a status. Notifications used sparingly. A console for your staff. Multilingual text and right-to-left layouts where your market needs them. Reports you actually read. Everything else is a later release, priced when the numbers say it will pay.

Checklist before the first call

  • Write one sentence on what customers will do in the app.
  • List the systems the app must talk to, if any.
  • Decide which route fits: branded, one-time build, or custom.
  • Gather your logo, colours and the content the app needs.
  • Decide who in your business will own the console and the accounts.
  • Pick the one number the app should move in its first quarter.

The numbers to expect

A branded app is live within days at a flat monthly plan. A one-time build is delivered in one to three weeks at a fixed price. A custom application is scoped in a week and delivered in eight to twelve weeks at a fixed price per release. Customised or more complex functionality is quoted separately before any work starts. The prices are on the GBCORP e-shop and do not change on the phone.

What the first month looks like

Week one, a short call about what customers will do in the app, then the choice of route. For a branded app, GBCORP sends a short form for brand and content, opens the store accounts in your name and configures the app; you see it on your phone within days and the web version is live on your domain. For a one-time build, the same, with a fixed delivery date and a hand-over of everything at the end. For a custom application, the first week is the scoping week and the second month starts the sprints. In every case, by the end of the first month you have an app you can show, an account you control and a price you already knew.

Mistakes businesses make when hiring an app developer

Hiring on price per hour and discovering the hours. Letting the developer open the store accounts and the cloud project in their own name. Starting with a custom build when a configured app would have proved the idea for a fraction. Paying for features nobody asked for because the developer suggested them. Launching to everyone at once instead of the ten customers who said they wanted it. Forgetting that the app needs a release every time the operating system changes, and having nobody to do it. Each is avoided by one question asked before paying, and the checklist above contains all of them.

Three businesses, three routes

A café that wants ordering and a loyalty card is the branded app: live within days at a flat monthly plan. A consultancy that wants a client portal it owns outright, with no monthly fee, is the one-time build: delivered in weeks at a fixed price, handed over complete. A logistics firm with a dispatch process no product covers is the custom application: scoped in a week, built in sprints, priced per release. All three are GBCORP, and the first call decides which.

Questions we hear first

How much does an app developer cost?

It depends on the route. GBCORP publishes flat prices for branded apps and one-time builds and quotes custom work per release after a one-week scope.

Do I need a developer near me?

No. The work is remote, the app ships to stores worldwide, and the console is a web page.

Can I start small and grow?

Yes. Many businesses start with a branded app and add custom releases where the numbers justify them.

What if I already have a website?

The app links to it, or GBCORP rebuilds both on one engine so content is managed once.

Where to start

The GBCORP custom app development hub explains the routes; the GBCORP One-Time Branded App Build is the priced product for a business that wants an app it owns. For the same question from the other side, read who can build an app for my business.

GBCORP operates across 17 countries on 4 continents through six pillars: AI & IT, Innovation, Sustainability, Infrastructure, Business Lounge, and EV's & Solutions.