Less paper spent on paperwork, less time spent on boring tasks, and fewer people shoulder-watching your phone in public transport.

We stand for less paper spent on paperwork, less time spent on boring tasks,

and less shoulder-watching in public transport.

This is a standard process we know from fixed priced projects vs. the process we use in Timepress.
Of course, it‘s just an example.

Oldschool vs. TIMEPRESS

Day 1

First meeting

First meeting. ✌

Day 2

Pricing the project

Getting all the necessary materials needed from the client. 📁

Day 3

Pricing the project

Start of the development. 💡

Day 7

The full description of the intended functionality is finished (if lucky)

The main software architecture is already designed. 🖥️

Day 14

Client waits

Client gets the first demo, and we proceed with continuous development and delivery. 🤨

Day 30

Waits…

We ask the pilot users for feedback, so we can adjust the project. 👥

Day 40

Waits…

We are still delivering and deploying the system piece by piece, so you can see the progress. 📈

Day 60

Still waits…

We move to another issue that is more urgent for the client at the moment. ⏰

Day 90

Keeps waiting…

We deliver more functionality, that was not part of the original description but it popped up and we still have time in the required time frame and budget. 🔮

Day 130

Keeps waiting…

End users keep commenting on new functionality, we continue developing the system. 👨‍💻

Day 180

Client gets something based on his 6 month old needs without any adjusting to the current situation in the company or the market, without any say in how well it’s actually executed.

Client has a running system used for around 5 months already. Battle proofed and adjusted to the ongoing needs of the company. 🤠