Try ABACUS TECH for One Week,

Free of Charge

Do you want to know if ABACUS TECH is the right partner for you? Here is your chance to evaluate our services and test potential developers. Try ABACUS TECH's services for free for one week and find out how we work, our development efficiency and other capabilities.

How To Start

  • Step 1: The preparation phase
  • Step 2: The execution phase – development sprint

Step 1: The preparation phase

The preparation phase serves to establish unobstructed discussions between the developer and the customer, explore the future software’s goals, and test potential solutions.


For the developer

The first thing to do when starting a free trial is to explore the client's development

needs, technical requirements, expectations and scope. Your goal is to ask questions

that relate to the customer's specific business objectives, the software and the results

they are trying to achieve with the software. By starting with general questions and

then moving into specific questions, you can get the big picture and understand how

the software fits into the client's vision.

Of course, no one expects to understand the intricacies of a company's operations

and other details in a week. The goal is to begin to understand and find common

ground between you and the client.

It is important to organise the work that can be done so that the implementation

phase runs smoothly. Once you have the necessary information and have begun to

understand your client's business processes, two key points should be explored and


1. What can you do in one week?

2. How can you do this?

Once you explore the possibilities for the work you can do in one week, try to set up a plan to complete said work. Here, you propose the deliverables, the scope, key performance indicators, and the roadmap for achieving the goal. The customer should then greenlight the proposal before you start with development.

Once you and the customer agree on everything and both are sure you understand each other, move on to the execution phase.


For the customer

Bring a product owner to the meetings. The ideal scenario would be that you approach the preparation phase with a high-level description of the requirements and in-depth user stories. But if you don’t have these, it’s okay; as long as you have a broad idea of what you need and communicate your expectations, the developer can work with this and properly explore the options.

These sessions should also help developers explore the competition, your software's

unique strengths, potential pitfalls and challenges to watch out for, and put everything

into context. This thorough preparation will help the developer create valuable software

for you and provide useful insights on how to achieve the desired results.

Another thing you should do as a client is to bring the product owner to the meeting.

The product owner is responsible for the project and has the authority to agree and

make decisions with the developer. Having a decision-maker/product owner is the best

set-up for a successful free trial, as the developer needs to be in constant communication with you.

Step 2: The execution phase – development sprint

The execution phase is where all the planning and the discussions come together; it lasts one week (40 work hours), and during the execution phase the customer sees what the developer is really capable of.

This phase is essentially a one-week development sprint – a short, time-boxed period where the developer strives to complete a set amount of work. The sprint is organized so that the customer always knows what’s going on with the project – what challenges the developer is facing, the progress they’re making, and how they’re solving the issues that arise.

Although the development is the main focus for the execution phase, there are other free trial aspects both the developer and the customer should be aware of.

One aspect is maintaining open and constant communication.


For the developer

Your tasks are to inform the customer of every progress or roadmap deviation and to provide the customer with a report at the end of each workday. It’s ABACUS TECH policy to keep everything transparent, so you as a developer should always strive to inform the customer about your decisions, your next move, your plans for the next day, etc. The reports don’t need to be detailed, but to provide an overall account of what you did for that day. They usually consist of:

1. A recap on what you worked on

2. The challenges you faced

3. What you plan to do for the next day

Next to the reports, you should include daily 10-minute standup meetings, where you have an open discussion with the customer and discuss the plans, your efforts, finished and outstanding tasks.

Having open and constant communication, producing various reports, and keeping everything transparent are the practices we follow both in free trial and later during cooperation, so you as a developer need to introduce the customer to ABACUS TECH’s best practices.


For the customer

Your tasks are to actively participate in the discussions and provide feedback to the developer. Development isn’t a straight path and communication shouldn’t only be one way, so coordinating the efforts is important for getting the results out of the free trial.