each team member naturally participates in Bytsolv’s marketing. How? We share knowledge, we consult. Bytsolv team members should understand business and how technology can be implemented in a business. And if you see someone who is is need, you talk to them, you share your knowledge with them. We don’t try to sell, instead we try to help and be a trustful person to the other one. When something comes up they will connect us and ask for help, this will transform in to a business. The most natural way of business.
Budgeting (Estimation)
For small projects, when we discuss a project, we listen to the customer and we trust on the gut. From the experiences of the previous project we share a pricing. In bigger projects we don’t have room to make such mistakes, so we do the BRD first, then pricing.
Project
Quotation → Agreement and Contracts → First Invoice.
Any project is considered as initiated after the advance invoice. Until then we consider it as a lead.
We don’t move forward without proper documentation of a project. At the end of the day, we need a single source of truth to rely on, and thats the project visualisation and doc.
Weekly plans and communication
Any project’s updates shall be shared to the customer on a weekly basis. All development cycle should be planned on a weekly basis. We should have milestones to achive for every week.
Customer Satisfaction
Progress Sharing
We share weekly progress. We include, what was planned for the week and what went right and what went wrong. The people who pay for the stuff to be ebuilt should have a full understanding of the project at any point. We are liable to share the updates timely. The progress sharing should via email which is the formal method. Additionally we share the progress via the the platform whichever is convenient for the customer.
For the progess sharing to be nice, everyone should share a weekly summary of what they did last week based on each project.
The weekly sumary shiuld be shared in the project channel in mattermost.
Project Delivery
Completion Communication
As we communicate everything every week, the client will natually know when we are gonna deliver the project. And every delivery event should be a meeting with the client and the people who communicated with the client. We explain everything to the client slowly one by one.
Completion Certificate
Once the delivery event is done, we give it to the client to playaround and implement. We requst for a project completion certificate from the customer by sharing a project completion certificarte template, which they can print in their letterhead and sign.
Post Delivery
Warranty Communication
The warranty of any project should be mentioned in the project contract initially. We usually give one-year long project warranty. Usually warranty covers bug fixes. We should know what’s a bug fix and a feature-request.
Warranty initiation should be informed to the customer early. The customer should be fully aware of what they can avail inside the warranty period. Incase a customer is not using the warranty period, we should remind them about the warranty.
On top of the warranty, we give 2 years of consultation via forum/chat. The customer can ask doubts, and questions to Bytsolv, and the team will respond to the queries based on the priority.
AMC Communication
The AMC of a project is usually written as a separate contract. Usually, an AMC starts at the end of the warranty period.
Announcement
If the project’s public announcement does not hurt the client’s business we will announce the projects publicly. This includes case study, experience sharing, team blogs etc.
Suggestions Doc (budget this research in the project cost)