Business software · internal tools · connected workflows
Custom business software built around your workflow.
When spreadsheets, email and existing apps no longer fit together, I help find the smallest useful solution. I design and develop internal tools, customer portals and integrations, from the first brief to deployment and handover.
I am Jan Kimla, an independent web and mobile app developer. You work directly with the person responsible for product design and implementation.
Describe your workflowWhat the solution can include
Internal tools and job workflows
When work gets lost between email and spreadsheets: one view of status, ownership, deadlines, source materials and the next action.
Customer portals
Let customers access their own documents, request status and completed work. Permissions determine which records each person may see.
Booking and capacity tools
Applications, people or resource availability, confirmations and changes. First I check whether a well-configured existing product would solve the problem.
Integrations and workflow automation
Move data between existing applications through supported interfaces. Design includes failure handling, repeated events and traceable processing.
Example briefs by business type
These are examples of possible briefs, not claims of completed customer projects.
Trade and service businesses
Request with source details → quote → job → invoicing handoff. The first step alone can be a useful project; you do not have to build the entire system.
Tutors and appointment-based services
Application → capacity check → confirmation → participant list. Individual appointments and group courses need different workflows.
Small teams and professional services
Request → assignment → approval → delivery. Access permissions and a clear status matter more than another dashboard.
A concrete product I built
Cestiq: a mobile app and portal sharing the same data.
Cestiq is my own live product for preparation for Czech driving tests. It connects a student app with a school portal in the browser and is available on iOS, Android and the web. The public administration demo uses fictional data.
How I designed and built Cestiq →
Technical evidence is not a guarantee of your business results. Cestiq does not replace a driving school’s statutory records.
From today’s workflow to a useful application
1. Walk through the real workflow
Show how you handle one job or request today, where errors occur and which tools you already use.
2. Choose configuration, integration or custom development
If an existing product solves the problem, rebuilding it is unnecessary. Custom development should cover a specific unmet need.
3. Validate the smallest useful version
A prototype tests one important journey. We distinguish working functionality, test data and the work still required before production.
4. Test and hand over
Before deployment, we check roles, failures and recovery within the agreed scope. Handover includes source code, accounts and operating instructions.
A bounded project, not an endless platform
Before starting, we separate development, licences, hosting, data migration and ongoing care. Scope changes are agreed as they arise. A prototype is not treated as production, and integration with any arbitrary application is not guaranteed.
Questions before building business software
How much does custom business software cost?
Cost depends on workflows, user roles, integrations and the condition of existing data. We scope one useful release first; the next estimate follows a written scope. Hosting, third-party licences and later development are separate items.
Do we have to replace our existing applications?
No. Keeping working tools and connecting the missing step can be more useful. Integration depends on each vendor’s API, permissions and terms.
Is a spreadsheet always the wrong solution?
No. For a simple view and a small team it may be the most economical option. A custom tool makes sense when recurring errors, permissions or workflow complexity justify maintaining it.
Can we work together remotely in Europe?
Projects can be discussed remotely. We agree the working language, scope, local tools and delivery conditions first. This is not a promise of ready-made localisation, accounting compliance or phone support in every European language.
Will we be locked to a single developer?
Agreed handover includes source code, access and documentation. The customer should control their accounts and data. Support scope, licence terms and export requirements are agreed before implementation.
Where does your current workflow slow you down?
Describe one typical job: who receives it, where the details go, what repeats and which step causes trouble. That is enough to start a useful conversation.