{"id":3096,"date":"2019-09-30T00:00:00","date_gmt":"2019-09-30T00:00:00","guid":{"rendered":"http:\/\/the-codest.localhost\/blog\/codests-good-practices-for-building-software-our-approach-to-customer-journey\/"},"modified":"2026-04-24T08:49:32","modified_gmt":"2026-04-24T08:49:32","slug":"codests-good-practices-for-building-software-our-approach-to-customer-journey","status":"publish","type":"post","link":"https:\/\/thecodest.co\/en\/blog\/codests-good-practices-for-building-software-our-approach-to-customer-journey\/","title":{"rendered":"Our approach to customer journey"},"content":{"rendered":"

Discovery call<\/strong><\/h2>\n

Having a brief idea on what the customer\u2019s project<\/a> is about, our team<\/a> starts exploring the cooperation potential from more detailed discovery call. Usually, we would love to know how your current engineering setup looks like, what do you struggle with, what bottlenecks do you identify with your product development<\/a>, what plans and deadlines do you have with your development pipeline, etc. to have a better understanding how we could address your needs.<\/p>\n

Defining needs<\/strong><\/h2>\n

Addressing the needs starts with defining and articulating them clearly. Sometimes our clients know exactly what they look for while other time we need to suggest the solution and ideal cooperation model by assessing the current state. In some cases, we begin with a short consulting assignment before moving on to a full-scope project engagement.<\/p>\n

\"software<\/p>\n

Project kick off<\/strong><\/h2>\n

To have a 360 degrees project view, it is crucial to let the project team members get to know each other and discuss the desired model of work, methodology, communication method, roles and responsibilities. Most often our partners in those discussions are CTOs<\/a>, Engineering Managers<\/a> or CPOs who drive the product<\/a> development pipeline. Once we reach clarity on all major subjects, we are ready to start lining up the project team.<\/p>\n

Contract signing<\/strong><\/h2>\n

Having all major points agreed, we finalise the arrangements with signing a contract and NDA(which we sometimes also sign at the early stage of contact if necessary or upon customer request). The framework for the contract is described in our detailed general terms and conditions document that is always reviewed by the client prior to engineering works launch.<\/p>\n

\"building<\/p>\n

Dev phase<\/strong><\/h2>\n

Our engineering team enjoys being challenged with difficult tasks and prove them deliverable in style. For the beginning of every successful long term cooperation, we always aim to prove our standards and quality of work with the trial projects. Usually, we establish certain milestones and benchmarks at the project launch that are reviewed with the client\u2019s team along the way as checkpoints. It leads us<\/a> smoothly to the summary of the project that is a validation of our engagement before the framework of long term agreement takes shape.<\/p>\n

Summary and long term agreement<\/strong><\/h2>\n

Summarising the project we evaluate together with the client the key metrics established at the beginning of development phase. Quality review, team\u2019s efficiency, estimated time and budget alignment are all important to verify before diving deep into the long term cooperation. We love hearing positive feedback from our clients and giving them a chance to taste our style of work before we join forces for the long term successful cooperation.<\/p>\n

Read more:<\/strong><\/p>\n