Ah, it’s ha.
We’ve got
your back.

Yes. Choose “Bespoke app / custom software” and describe what happens today, who uses it and what you want to improve. The checklist is inspiration, not a catalogue of limits. We assess feasibility, dependencies and cost before committing to a build.

Yes. Use the bespoke route for a connected project and describe both. We identify shared content and accounts, then scope the website, backend and each app separately. A website budget does not automatically include Apple or Android apps.

Possibly. Show us the steps and where errors, retyping or delays occur, using fictional or redacted examples at first. We can explore a focused workflow with forms, records, approvals or summaries. We establish a baseline and agree what improvement to test rather than promise a saving we have not measured.

We assess the exact products, supported APIs or exports, licences and authorised account access first. Some connections are straightforward; others need paid access or may not be possible. We agree what data moves, who can see it and how failures are handled before building.

Yes. We listen to the founder, managers and people doing the work, then suggest a manageable first version. Your team supplies operational expertise; we contribute design and technical judgment. Specialist advice or paid discovery is agreed when the project requires it.

We agree the management area during planning. At handover you receive the correct address or approved app access route, your own named administrator account and a walkthrough. We help you sign in, set up any agreed multi-factor authentication and understand recovery. You do not need to edit code to use the management features we have built for you.

Yes, where role-based access is included in the scope. We map who should create, view, approve or export each kind of record and test those rules. Being a manager does not automatically give access to all personal, finance or HR information.

We agree the content you need to change—such as services, text, photos, menus or opening hours—and provide suitable editing controls. Video tutorials show the actual process. New functionality and changes outside those controls need a separate development task.

For a bespoke commission, the agreement identifies the rights transferred after the agreed payments, source files and handover. Third-party and reusable components keep their stated licences. For a ha. product, you license our software: your branding and business data remain yours, while ha. retains the product core. These are different offers, made clear before you commit.

A private browser app can use a sign-in address on the agreed devices without a separate app download. Apple, Android, offline operation and managed private distribution are separately scoped where needed. A hidden link alone is not security: access controls must protect the data.

We agree your branding and any discreet linked “Powered by ha.” credit. Bespoke handover identifies source, setup instructions, accounts and component licences so another developer can maintain the agreed work. A licensed ha. product follows its own access, export and exit terms; it does not include ownership of the core source.

We explain which accounts you need, who owns them, their costs and who renews them. Where appropriate, accounts are set up in your business’s name and you invite us with the access needed. We guide setup and handover; never put passwords, API keys or real customer records in this enquiry form.

Yes—we plan the rollout, not just the screen design. Your proposal lists setup tasks, supported devices, initial access checks, training or video tutorials and who signs off readiness. Hardware, on-site visits and larger training sessions are itemised. We confirm your team can complete the agreed core tasks before project acceptance.

We can scope supported equipment, configuration and workflow testing. You approve the specification, quantities, warranty, support life and costs before purchase. Equipment is not included in a software allowance unless expressly stated. We do not assume a phone camera can read every label in every workplace.

We first review lawful access, export formats, data quality and what must be retained. Migration, backups, checks and any downtime are planned explicitly. We use fictional data for early development and agree secure handling before receiving real records.

We write down the important tasks and supported devices, show usable stages and test those journeys with you. Permissions, key integrations and recovery responsibilities are checked where included. You review against agreed acceptance criteria; store releases and third-party approvals have separate dependencies.

The website slider illustrates an initial website scope and reserves room for selected extras. The bespoke route asks for a development budget without inventing a feature bundle. Product enquiries ask about setup and monthly preferences. None is a quote, order or guarantee of availability; a reviewed proposal comes next.

Tell us what you can comfortably invest and which outcome matters first. We may propose a focused landing page, discovery, a prototype or a smaller first release. We explain what is excluded and what a later phase would need. Staged delivery and payment milestones are agreed in writing.

Depending on the project: hosting, domains, storage, email, paid licences, payment processing, app accounts or device management. We identify known costs and usage assumptions before commitment. Optional bespoke support is separate; a product licence would specify which services are included.

Yes. Optional monthly support for bespoke work is scoped with tasks, allowance, response arrangements and price. Smaller agreed follow-up tasks are £60/hour with an estimate and approval before starting. Larger features are quoted separately. Product support would follow the product’s own service terms.

We agree a schedule after reviewing scope, capacity, customer inputs and external dependencies. We can design and test a clearer customer journey, but we do not guarantee sales, rankings or store approval. Changes and delays are discussed with you.

Your brief is saved privately for the ha. team to review. Keep the reference shown after submission. We use the reply address you provide to discuss the project; submitting creates no order, payment or subscription.