Realities
There are things we need to be clear about before we start working together. Your time, money, and business matter. So do the people and the work behind the system.
These are the conversations worth having before someone says, “Ay, akala ko kasama na ’yan.”
Yes, we do system customization. But you need to have time for it, too.
We do system customization, but that’s only if you have time to coordinate with us and to actually be patient. That’s also going to increase the cost.
We need you to explain how your business works, answer questions, review what we’ve prepared, and give us proper feedback. Someone from your team has to be available and able to make decisions.
Hindi puwedeng “bahala na kayo,” tapos pagdating ng output, “bakit ganito?” We need to work on this together.
And yes, sometimes your “small change lang” affects several other parts of the system. We have to study it, build it, and test it properly. That takes time and work.
We’ll discuss the scope, cost, and expected timeline with you. If the requirements change along the way, those may change, too. Customization needs a budget, your participation, and a reasonable amount of patience.
We need proper information from you. Hindi po mind reader ang system.
We need correct business details, records, and instructions. If the information you give us is incomplete or incorrect, that will affect the work.
We can help identify issues and explain what needs to be corrected. But we cannot guess which of your three spreadsheets is the updated one, especially if all three are named “FINAL.”
Your timeline also depends on you.
We can prepare a schedule, assign people, and make time for your implementation. We also need you to submit the requirements, answer questions, and approve things when needed.
If we’ve been waiting two weeks for your reply, those two weeks are part of the timeline. Hindi po naka-pause ang calendar habang hinihintay namin kayo.
We both have things to do to keep the project moving.
The system can be easy to use. You still need to learn how to use it.
Someone from your team needs to attend the training, pay attention, and actually try the system.
Please send the people who will be doing the work. If the person attending will explain everything to the actual user later, that is another opportunity for instructions to become a completely different story.
Madali gamitin does not mean alam mo na agad.
Keeping your existing system may still require work from your existing provider.
This is especially relevant for Eksphi API. You can keep your current system, but we still need to understand how it works and how it can connect.
Your provider or IT team may need to give us documentation, provide access, or make changes on their side. They may also charge for that work.
“May API naman kami” is a good start. We will still need something more technical than that sentence.
Your setup fee has a scope.
We need to agree on what is included, what we’re implementing, and what each side is responsible for.
Additional branches, integrations, reports, workflows, or changes may require additional work and cost. We should discuss those before proceeding.
“Nandiyan na rin naman kayo” is usually the beginning of another request. Sometimes that request is small. Sometimes bagong project na pala.
Technology can have problems. That is why maintenance and preparation matter.
Servers, internet connections, devices, and external platforms can experience problems. We work to reduce the chances of disruption and prepare for issues when they happen.
We also need to identify where the problem is coming from. Some things are within our control. Others require action from another provider.
We will take the problem seriously. Pero hindi namin puwedeng i-restart ang buong internet.
Your business will change. The system may need to change with it.
You may open another branch, increase your transaction volume, change your processes, or encounter new requirements.
Those changes can affect your setup, infrastructure, and service needs. We need to review them with you and explain what adjustments are necessary, including any effect on cost.
The setup for one store may need some adjustments when you suddenly have twenty. Congratulations, by the way. But please tell us before opening day.
We need useful details when you report a problem.
Tell us what happened, what you were trying to do, and what you saw on the screen. An error message, screenshot, and approximate time can help us investigate.
“Ayaw gumana” tells us that you’re having a problem. We will still need to find out which part.
Please also tell us if something was changed before the issue started. Hindi ito interrogation. We’re trying to fix the right thing.
Eksphi Lite is free. Human support is not included.
Lite is a simple starting point for microbusinesses. You can use it, become familiar with digital invoicing, and earn XP Points toward future benefits as your business grows.
If you need human assistance, guided implementation, or more involved services, we need to discuss the appropriate Eksphi offering.
We want Lite to stay useful and manageable. Giving it every feature and service would eventually make the word “Lite” a little questionable.
We still need someone who can make decisions.
We’re happy to coordinate with your staff, management, IT team, accountant, and other people involved. But we need to know who can approve the requirements and give the final direction.
If one person says yes, another says no, and a third person introduces an entirely different process, we need to settle that before continuing.
Internal alignment is part of implementation. Hindi namin puwedeng i-configure ang system based on whoever spoke last.
And here’s what we commit to.
The realities go both ways. These are the things we take seriously on our side.