Start by documenting the workflow you need to improve, then check whether a ready platform such as ChapFlow, MojaDesk or myDuka already fits. Commission custom software only when unique rules, integrations or scale require it. Budget for training and support, not only the first build, and ship a useful first version before you expand.
Write the process as it exists today
List who does each step, which tools they open, and where mistakes or delays happen. If orders arrive on WhatsApp, live in a spreadsheet, then get retyped into an invoice, that is the system, even if nobody named it. A custom project that ignores that path will be ignored by staff. Include peak-volume days, not only a quiet Tuesday.
- Is the need mainly inbox, orders, delivery, menus, CRM or billing?
- Do multiple teams need shared visibility?
- Which data must connect to existing systems?
- Who will own content and admin after launch?
Ready platform versus custom build
Prefer ChapFlow when sales, projects, people and billing should share one workspace. Prefer MojaDesk for a unified customer inbox, myDuka for a digital shop, DROP-IT for delivery operations, or Smart Menu for restaurant QR menus. Move to custom development when those products cannot cover critical rules without awkward workarounds. Custom cost is a range, not a sticker: it follows users, integrations and how unique the workflow is. We quote after a brief, we do not invent a generic software price here.
How long a custom system takes
A focused first version for a well-described workflow can ship in a matter of weeks once decisions are made. Broader systems with many roles, reports and integrations take months because discovery, design, build, testing and training all need calendar time. The longest delays are usually waiting for sample data, approvers or a decision on who owns the admin. We would rather ship a narrow useful release than a late everything-app.
- Discovery and a written scope for the first version.
- Design of the main screens and data model.
- Build and weekly reviews with real sample records.
- Testing, training and a support path after go-live.
Source code and products
Ownership for custom work is set in the project agreement. Ready platforms such as ChapFlow remain Site Weavers products that you use under their published terms. Do not assume you automatically own a SaaS codebase because you subscribe. Ask the question in writing before work starts.
Common mistakes
Starting a custom build when ChapFlow or another product already fits. Skipping training. Expanding scope every week without changing the deadline. Choosing a vendor who cannot meet in your time zone. We work from Dar es Salaam and collaborate remotely across East Africa for a reason: you should be able to reach the people who built the system.