← Home

KARVANIS SERVICE / CUSTOM BUSINESS APPLICATIONS

Custom business applications

When off-the-shelf software demands too many compromises, I build around the way your team works. Every screen, role and automation serves a use case validated with your users.

Describe my need

01 / Where it fits

Where it fits

Is this the right starting point?

Several people need to view, update or approve the same records: a business application helps organise that work. If a single calculation in a file resolves the need, a smaller automation project may be more appropriate.

01

Business-critical files

Replace a fragile mix of spreadsheets, emails and shared documents.

02

Specific workflows

Digitise rules or approvals that are unique to your activity.

03

Legacy internal tools

Modernise an ageing application without losing business knowledge.

02 / A controlled implementation

A controlled implementation

I start with a real workflow, test an initial version with you and develop the solution in stages.

  1. 01Observe the real work
  2. 02Prototype with users
  3. 03Deploy, document and support

An example of a first phase

Follow a request from creation to completion

This workflow illustrates one possible approach. Your project is defined around how your business works.

  1. Create a record

    The person enters the necessary information in a screen suited to their role. Required fields help them prepare a complete record.

  2. Review and decide

    The person responsible sees the requests needing attention. They can approve one or ask for a correction, following the agreed rules.

  3. Check progress

    Authorised users view the status and history. An export brings together the information needed for administrative follow-up.

The result to check

See where each request stands, which action is needed and what information explains its status.

What the quote should clarify

  • The users, permissions and approval stages
  • The screens, statuses and rules for moving between stages
  • The data to migrate and exports needed
  • The checking scenarios and support for getting started

When files are no longer enough

A spreadsheet remains useful while its operation is clear. Difficulties arise when several versions circulate, approvals happen by email or only one person knows the rules. A custom application can organise these activities into a shared workflow.

Design around real user roles

The person entering information does not necessarily need the same tools as the person checking it or preparing reports. Together, we identify what each role needs to know, which actions it may take and where approval is required. Each person gets the information and actions they need in a clear interface.

Turn examples into screens

I start with a representative situation, then describe entry, possible errors, corrections and the expected result. A first workflow allows users to assess the choices. Their feedback helps refine the details before the application grows.

Prepare for migration and change

Importing existing files requires checking their structure, duplicates and data quality. Together, we identify the information to retain and the exports people need. Future requirements are also discussed, so the first phase remains coherent without building everything at once.

Internal project: the workflows behind BX Cars

BX Cars connects a booking request, confirmation by the agency and rental follow-up. This internal project illustrates the connection between a public website, management records and an Android application.

Explore this project

Questions to discuss before starting

How long does a project take?

Timing depends on the workflows, data availability and required connections. The first conversation identifies these dependencies. We then agree on scope and review stages; a sound estimate requires understanding how your team works.

What budget should I expect?

The budget follows the agreed scope: users, rules, screens, data migration and external services. We can start with one priority workflow and define a useful first phase together. Any recurring costs should be clarified alongside the quote.

Who owns the code and data?

Deliverables, code rights, third-party licences and access arrangements should be defined in the contract. I discuss these points before starting, so you know what will be handed over and how your data can be retrieved.

How do we plan for continuity?

Continuity requires suitable documentation, clear access arrangements and a backup and recovery procedure. Maintenance, hosting responsibilities and any future handover to another provider should be agreed according to your project’s needs.

Direct contact, through to handover

I design and develop the solutions presented here. You speak directly with the person building your project. Together, we agree on review stages, access to hand over and documentation your team needs.

Planning also covers retrieving your data, backups, and arrangements for maintenance or a handover to another developer. These are defined within the agreed scope.

03 / CONTACT

Is a process still slowing your team down?

Tell me how it works today. A first 30-minute conversation helps us explore a practical starting point together, with no obligation.

Describe my need