How we work
Project delivery without subsequent surprises
When commissioning software, the principal concern is generally not price but uncertainty about how the project will proceed. The following sets out the course of a project, the input expected from the client and what is delivered on completion.
Typical circumstances
Circumstances in which clients most often engage us
If the circumstances described correspond to your situation, we have practical experience of comparable projects.
Operations managed through spreadsheets
A core process depends on a spreadsheet created several years ago. The solution functions, but only one employee understands it, it is sensitive to changes in data structure, and no one assumes responsibility for its maintenance.
Systems that do not exchange data
The same data is entered into the ERP, transferred to the CRM and exported to a spreadsheet for warehouse purposes. Errors are identified late and the source of discrepancies is difficult to establish.
Off-the-shelf covers only part of requirements
A system suitable for most organisations in the industry has been deployed, yet the processes that differentiate your business are still performed manually, outside the system.
The system is in use but unmaintained
The application was developed several years ago, the original author is no longer available, no documentation exists, and implementing changes requires a disproportionate period or does not occur at all.
The previous supplier withdrew from the project
The project was suspended before completion; source code exists but without documentation or anyone familiar with it, requiring a decision on continuation or redevelopment. We regularly assume such projects.
Licence costs exceed the cost of development
As the number of users has grown, annual licence and customisation fees have become a significant item, prompting consideration of whether developing a proprietary system is justified.
Project flow
Four project phases and the input expected from the client
- 01
Conversation and estimate
1-2 weeksWe analyse the business requirement, existing systems and identified constraints. We then provide an indicative scope and cost range, or a recommendation that the project not proceed.
Client involvement: One meeting of approximately one hour and access to the employees who operate the process daily.
- 02
Analysis and specification
2-4 weeksWe document the process to a level sufficient for development. The result is a document comprehensible to both management and the development team, separating mandatory requirements from those scheduled for a later phase.
Client involvement: Two to three working sessions. This phase requires the greatest client involvement and is the only one in which changes to requirements incur no additional cost.
- 03
Iterative development
depends on scopeDevelopment proceeds in two-week cycles. At the end of each cycle we present the progress achieved, allowing the direction of development to be adjusted at minimal cost.
Client involvement: Approximately half an hour every two weeks to review progress.
- 04
Rollout and beyond
2-6 weeks + ongoingData migration, a parallel run alongside the existing system, role-based training and support during the first weeks of operation. The engagement then transitions to maintenance.
Client involvement: Employee time for training and an adjustment period during the first two weeks of operation.
Transparency
Matters we set out in advance
An estimate issued without analysis is not binding
A precise price quoted before analysis is generally subject to later revision. We therefore provide a range at the initial stage and confirm scope and cost following completed analysis.
Changes to scope affect delivery dates
The majority of project delays result from requirement changes agreed during delivery. All changes are therefore recorded in writing, with their effect on schedule and cost stated at the same time.
The most demanding element is not development
The most demanding element of a project is achieving genuine adoption by users. Projects generally do not fail for technical reasons but at the deployment stage, to which we allocate more time than is customary.
In certain cases we recommend not proceeding
Where an off-the-shelf product meets your requirements at lower cost, we will advise accordingly and decline the project. Long-term credibility is of greater value to us than an individual contract.
What you get
What you acquire on completion of the project
- Source code and complete documentation in your ownership
- Standard technologies, without dependency on supplier tooling
- Documentation sufficient for another team to assume maintenance
- Access to all user accounts, databases and environments
- An agreed maintenance arrangement, with the option of transferring to another supplier
Verifiable
Independently verifiable credentials
In place of testimonials that cannot be verified, we set out concrete information about the company, its partnerships and its projects.
Bitrix24 Gold Partner, five years running
The only Gold Partner in Croatia. The status is awarded by the platform vendor on the basis of the number and quality of completed implementations and is reviewed annually.
Verification in the official partner directory Bitrix24 servicesA research project with the Faculty of Electrical Engineering
We are part of the EnergoLoyalty project worth 851.638,37 €, co-financed by the EU, in partnership with the Faculty of Electrical Engineering and Computing. Participation in the project is subject to technical and financial review.
A registered company based in Zagreb
Appliment d.o.o., VAT ID 32696391835, registered with the Commercial Court in Zagreb (MBS 081526433). You contract with a registered company that has been on the market since 2013.
4.9 rating based on 27 Google reviews
Reviews are published independently by clients and are neither edited nor selected.
View reviewsReasons for the absence of a client list
A significant proportion of our projects concern internal business systems covering sales processes, pricing, margins and warehouse operations. Clients generally do not publish such information, and we disclose nothing without their express consent. During a meeting we present specific projects and, subject to client consent, facilitate direct contact.
Ready for the next step in digitalising your business?
If you are looking for a partner able to see a project through to completion, we suggest an introductory meeting. The meeting is non-binding and serves to establish your requirements.