Your own application instead of a subscription

When to consider your own application

• The bill grows with every person you add, even though everyone uses the same few features.
• A feature you need is only available on a higher plan, bundled with extras you never use.
• The software imposes stages, fields or reports that do not fit your work.
• Your team enters the same data in several tools and combines the results in a spreadsheet.

What we can build

We define the scope around tasks your team performs every day. The application can replace one tool or bring together work currently spread across several programs.

It does not have to be a web application. We can build desktop software for Windows, Linux or macOS, or a mobile app for Android or iOS. We agree which devices it should run on and whether it also needs to work offline.

• CRM: contacts, conversation history, quotes and reminders built around your sales process.
• Job management: assignments, deadlines, status updates, photos and completion reports.
• Bookings: staff calendars, room or equipment availability and notifications.
• Client portal: documents, requests, approvals and progress updates.
• Document workflow: requests, expense approvals and a record of decisions.
• Reporting: figures from your existing systems without copying data every week.

iPhone: a PWA or an App Store app

For iPhone, we usually recommend a PWA: a web application you can add to the phone’s Home Screen. It also works in a browser on a computer and other devices. It does not require App Store publication or an Apple Developer membership. Before choosing it, we check that the browser supports the features you need.

If your iOS app is to be published on the App Store through your own account, allow for the Apple Developer Program fee: 99 USD per year, billed in local currency where Apple offers it. This is Apple’s developer account fee, not a subscription to use your application.

We can also agree to publish through CloudTech’s account. In that case, we agree the cost and support terms individually.

Current Apple Developer Program fee

Android: publishing on Google Play

To publish your Android app on Google Play through your own account, registering that account costs a one-time fee of 25 USD. This is Google’s developer account registration fee.

For personal accounts created after 13 November 2023, Google requires a closed test with at least 12 testers opted in continuously for a minimum of 14 days. You then apply for production access and describe your testing process. We account for these requirements in the launch plan.

We also have our own Google Play account. We can agree to publish through CloudTech’s account, with pricing, publication support and subsequent updates arranged individually. The app is still subject to Google’s review.

Google Play account fee

Testing requirements

What you receive at handover

You receive the working application, source code, documentation and deployment configuration. The contract sets out your rights to the code we create and identifies third-party components and their licences.

We agree where the system runs and who can access the data. We hand over the accounts, credentials and operating instructions. CloudTech, your team or another supplier can develop the application further.

What you pay for after launch

We do not charge an access subscription or per-user fees for the application we build. Development costs and payment terms are agreed before work starts. You commission further features separately.

An application needs maintenance. Before you decide to build, we also set out these costs:

• Servers or hosting, domain registration and backups. More traffic or data can increase infrastructure costs.
• Security updates, monitoring and fixes. We agree the scope and who is responsible; you can appoint another supplier.
• External services where needed: SMS, payments, maps, email or APIs. Their providers may charge their own fees.

Will it cost less than SaaS

We compare your current subscriptions with development, data migration and maintenance over the same period. We account for user numbers, integrations and time spent on manual work. That gives us a basis for deciding whether the change pays off.

If a ready-made product fits your process and costs little, a custom system may be more expensive. When requirements change often, it also helps to establish which features your team actually uses first. We will tell you if keeping your current tool makes more sense.

How we move from your current tool

• We review the features you use, your bills and examples of everyday tasks. We check data export options and available integrations.
• We agree the first version, cost, schedule and acceptance criteria. You see what is included and what can wait.
• We build and demonstrate working parts. Your team tests them against actual work scenarios.
• We run a trial data migration, check the results and agree the switch. Cancellation of the old tool is planned after acceptance of the new system.

Tell us what you use today

Send the names of your tools, the number of users and your approximate monthly bill. Describe what is missing or still needs manual work. That is enough to start a conversation about the scope and cost of your own application.

Tell us about your application