{"id":1139,"date":"2026-11-18T08:19:29","date_gmt":"2026-11-18T08:19:29","guid":{"rendered":"https:\/\/zamacore.com\/blog\/?p=1139"},"modified":"2026-11-18T08:19:29","modified_gmt":"2026-11-18T08:19:29","slug":"low-code-software-development-in-kenya","status":"publish","type":"post","link":"https:\/\/zamacore.com\/blog\/low-code-software-development-in-kenya\/","title":{"rendered":"Low Code Software Development in Kenya: Speed Without a Dead End"},"content":{"rendered":"<p><a href=\"https:\/\/zamacore.com\/blog\/e-commerce-development-in-kenya\/zamacore_-built-for-whats-next\/\" rel=\"attachment wp-att-978\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-978\" src=\"https:\/\/zamacore.com\/blog\/wp-content\/uploads\/2026\/10\/Zamacore_-Built-for-Whats-Next.png\" alt=\"Low Code Software Development in Kenya\" width=\"1254\" height=\"1254\" srcset=\"https:\/\/zamacore.com\/blog\/wp-content\/uploads\/2026\/10\/Zamacore_-Built-for-Whats-Next.png 1254w, https:\/\/zamacore.com\/blog\/wp-content\/uploads\/2026\/10\/Zamacore_-Built-for-Whats-Next-300x300.png 300w, https:\/\/zamacore.com\/blog\/wp-content\/uploads\/2026\/10\/Zamacore_-Built-for-Whats-Next-1024x1024.png 1024w, https:\/\/zamacore.com\/blog\/wp-content\/uploads\/2026\/10\/Zamacore_-Built-for-Whats-Next-150x150.png 150w, https:\/\/zamacore.com\/blog\/wp-content\/uploads\/2026\/10\/Zamacore_-Built-for-Whats-Next-768x768.png 768w\" sizes=\"auto, (max-width: 1254px) 100vw, 1254px\" \/><\/a><\/p>\n<p><a href=\"https:\/\/zamacore.com\">low code software development in Kenya<\/a> usually arrives through a finance team that has waited eight months for a small approval app.<\/p>\n<p>Someone discovers a platform, builds the thing in a fortnight, and the business saves real money before anybody asks about support.<\/p>\n<p><a href=\"https:\/\/zama.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> is a good answer to that problem, and a poor answer to several others.<\/p>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_86 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/zamacore.com\/blog\/low-code-software-development-in-kenya\/#Where_Low_Code_Earns_Its_Place\" >Where Low Code Earns Its Place<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/zamacore.com\/blog\/low-code-software-development-in-kenya\/#The_Citizen_Developer_Temptation\" >The Citizen Developer Temptation<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/zamacore.com\/blog\/low-code-software-development-in-kenya\/#Data_Ownership_and_the_Exit_Clause\" >Data Ownership and the Exit Clause<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/zamacore.com\/blog\/low-code-software-development-in-kenya\/#M-PESA_and_eTIMS_Integrations\" >M-PESA and eTIMS Integrations<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/zamacore.com\/blog\/low-code-software-development-in-kenya\/#Per-User_Pricing_at_Two_Hundred_Seats\" >Per-User Pricing at Two Hundred Seats<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/zamacore.com\/blog\/low-code-software-development-in-kenya\/#Performance_Ceilings_You_Only_Meet_Later\" >Performance Ceilings You Only Meet Later<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/zamacore.com\/blog\/low-code-software-development-in-kenya\/#Shadow_IT_and_the_Spreadsheet_Estate\" >Shadow IT and the Spreadsheet Estate<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/zamacore.com\/blog\/low-code-software-development-in-kenya\/#Governance_and_Change_Control\" >Governance and Change Control<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/zamacore.com\/blog\/low-code-software-development-in-kenya\/#When_Custom_Code_Becomes_Cheaper\" >When Custom Code Becomes Cheaper<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/zamacore.com\/blog\/low-code-software-development-in-kenya\/#Three-Year_Total_Cost\" >Three-Year Total Cost<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/zamacore.com\/blog\/low-code-software-development-in-kenya\/#Prototyping_Without_Committing\" >Prototyping Without Committing<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"https:\/\/zamacore.com\/blog\/low-code-software-development-in-kenya\/#Approvals_Audit_and_the_Finance_Sign-Off\" >Approvals, Audit and the Finance Sign-Off<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-13\" href=\"https:\/\/zamacore.com\/blog\/low-code-software-development-in-kenya\/#Vendor_Lock-In_in_Practice\" >Vendor Lock-In in Practice<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-14\" href=\"https:\/\/zamacore.com\/blog\/low-code-software-development-in-kenya\/#Skills_Handover_and_the_Team_You_Keep\" >Skills, Handover and the Team You Keep<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-15\" href=\"https:\/\/zamacore.com\/blog\/low-code-software-development-in-kenya\/#Integration_Depth_and_the_ERP_Boundary\" >Integration Depth and the ERP Boundary<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-16\" href=\"https:\/\/zamacore.com\/blog\/low-code-software-development-in-kenya\/#Security_Reviews_and_the_ODPC\" >Security Reviews and the ODPC<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-17\" href=\"https:\/\/zamacore.com\/blog\/low-code-software-development-in-kenya\/#Scaling_From_One_Department_to_a_Group\" >Scaling From One Department to a Group<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-18\" href=\"https:\/\/zamacore.com\/blog\/low-code-software-development-in-kenya\/#The_Decision_Rule\" >The Decision Rule<\/a><\/li><\/ul><\/nav><\/div>\n<h2><span class=\"ez-toc-section\" id=\"Where_Low_Code_Earns_Its_Place\"><\/span>Where Low Code Earns Its Place<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Low code suits processes that are simple, internal and still changing, used by a known group of people for a defined purpose.<\/p>\n<p>An approval workflow, a site inspection checklist, a leave request, a supplier onboarding form: these are forms plus rules plus a queue.<\/p>\n<p>Count the integrations before the forms. A form that must read stock and write an invoice is an integration project wearing a form&#8217;s clothes.<\/p>\n<p><a href=\"https:\/\/dexa.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should name the shape before naming the platform. If the requirement is a form and a report, low code fits.<\/p>\n<p>If the requirement is a pricing engine, a payroll calculation or a reconciliation across three systems, it probably does not.<\/p>\n<p>The test is the number of decisions per transaction. Two or three decisions, each with a clear rule, is low code territory.<\/p>\n<p>Twenty decisions with exceptions, delegations and a regulator watching is not, however good the demo looks.<\/p>\n<p><a href=\"https:\/\/pawa.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> also suits the department that needs something this quarter and can accept a standard interface.<\/p>\n<p>Custom user experience, offline field work and high-volume transactions are the edges where the platform starts to fight back.<\/p>\n<p>Any process with a statutory deadline belongs on the careful list as well, because a missed filing is not a user experience issue.<\/p>\n<p>Write the fit criteria before the demo, because a good sales engineer can make any platform look suitable for anything.<\/p>\n<p>Score each candidate process out of ten on volume, decision count, integration count and expected life. Below twenty-five, look again.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"The_Citizen_Developer_Temptation\"><\/span>The Citizen Developer Temptation<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>The promise is that business people build their own tools, and the finance department stops waiting for IT.<\/p>\n<p>The first two apps are a triumph. The third is a stock tracker that duplicates the ERP, and the fourth is a payroll calculation nobody can audit.<\/p>\n<p><a href=\"https:\/\/pms.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> usually fails not at the first app but at the twentieth, when the builders have left their departments.<\/p>\n<p>Citizen developers need a lane, not a ban. Let them build forms, checklists and small trackers, with a register and a review date.<\/p>\n<p>Give them a sandbox, a naming convention and a template, and the apps arrive tidier than anything built in a personal account.<\/p>\n<p><a href=\"https:\/\/estateadmin.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should define what they may not touch: money movement, statutory returns, patient data, anything involving an external party.<\/p>\n<p>Every citizen-built app needs an owner, a purpose and an expiry date. Without those three, the estate fills with orphans.<\/p>\n<p>Publish the register where IT can see it. A list nobody reads is not governance, it is an archive.<\/p>\n<p>Encourage the business analyst who understands the process. Discourage the enthusiast who mainly enjoys the tool.<\/p>\n<p><a href=\"https:\/\/churchesadmin.com\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> with a platform team behind it turns curiosity into capacity, rather than into a support queue for IT.<\/p>\n<p>Review the register every quarter and retire what nobody uses. Deletion is a governance function, not a loss.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Data_Ownership_and_the_Exit_Clause\"><\/span>Data Ownership and the Exit Clause<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>The data in a low code app belongs to the business, but the shape it takes can belong to the platform.<\/p>\n<p>Ask three questions before the first record: where does it live, what can I export, and what happens on termination.<\/p>\n<p>Add a fourth: who else can read it. A platform that shares data with its own analytics service has changed the answer.<\/p>\n<p><a href=\"https:\/\/vega.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should insist on a full export in a documented format, including attachments and history, not only current rows.<\/p>\n<p>A spreadsheet of the main table is not an exit. Look for the audit history, the workflow states and the attached documents.<\/p>\n<p>A restore should be tested into a clean environment, because a backup nobody has restored is a rumour.<\/p>\n<p>Data residency matters under the Data Protection Act. Know which country holds the replica, not only the primary database.<\/p>\n<p>Ask for the sub-processor list. The platform you contracted may run on three others you have never assessed.<\/p>\n<p><a href=\"https:\/\/dereva.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> with a deletion certificate at exit avoids the awkward discovery that records survive the contract.<\/p>\n<p>Put the exit test in the agreement as a deliverable, with a date and a named owner on each side.<\/p>\n<p>A platform that cannot be left cheaply is a platform that can raise its price with confidence.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"M-PESA_and_eTIMS_Integrations\"><\/span>M-PESA and eTIMS Integrations<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Almost every Kenyan business process eventually touches a payment and a tax invoice.<\/p>\n<p>M-PESA integration means Daraja, a shortcode, credentials, callbacks and a reconciliation that survives a timeout.<\/p>\n<p>Go-live on Daraja needs a production shortcode, a whitelisted callback URL and a certificate that does not expire quietly.<\/p>\n<p><a href=\"https:\/\/jaat.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should treat the payment as a state machine: initiated, pending, confirmed, failed, reversed. A callback is not a guarantee.<\/p>\n<p>Test the timeout path first. A customer who pays twice because the first callback was slow is a refund and a complaint.<\/p>\n<p><a href=\"https:\/\/wito.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> must store the M-PESA receipt number against the transaction, or the bank reconciliation becomes guesswork.<\/p>\n<p>eTIMS integration is stricter. The invoice payload must carry the right tax treatment, and the response must be stored.<\/p>\n<p><a href=\"https:\/\/awasam.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should treat a rejected invoice as a first-class outcome, with a queue, a reason and a person responsible.<\/p>\n<p>Both integrations are regulated and both change. Keep the mapping in one place, documented, with a test environment.<\/p>\n<p>Reconcile daily between the platform, the payment provider and the bank. Three sources that agree are worth more than one that is trusted.<\/p>\n<p>Sandbox success is not production readiness. Run a small live pilot with a real shortcode before the volume arrives.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Per-User_Pricing_at_Two_Hundred_Seats\"><\/span>Per-User Pricing at Two Hundred Seats<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Low code is priced per user per month, and the number looks small until it meets a Kenyan headcount.<\/p>\n<p>At thirty dollars a user, two hundred users cost seventy-two thousand dollars a year before implementation begins.<\/p>\n<p><a href=\"https:\/\/saseni.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should model the licence against the whole population, not the department that started the project.<\/p>\n<p>Separate the people who create from the people who approve and the people who only read. Many platforms price them differently.<\/p>\n<p>Read-only users can be most of the organisation. If they are charged as full seats, the business case changes shape.<\/p>\n<p><a href=\"https:\/\/prim.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should count external users: suppliers, agents, field staff and customers, because guest pricing is often higher.<\/p>\n<p>API calls and storage form the second invoice. A busy integration can exhaust a plan that looked generous in the demo.<\/p>\n<p><a href=\"https:\/\/rentaldesk.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should include the renewal uplift. Ten per cent a year compounds faster than most budgets allow.<\/p>\n<p>Compare the three-year licence total with the cost of a custom module maintained in-house.<\/p>\n<p>A platform that costs more each year than the process is worth is a subscription to overhead.<\/p>\n<p>Negotiate on volume before the pilot ends. Bargaining power exists while the contract is unsigned and disappears afterwards.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Performance_Ceilings_You_Only_Meet_Later\"><\/span>Performance Ceilings You Only Meet Later<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Every low code platform has a ceiling, and the demo never reaches it.<\/p>\n<p>Ten thousand records behave beautifully. A million records with a report across four tables is a different product.<\/p>\n<p><a href=\"https:\/\/fama.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should be tested with production-like volume before rollout, not after finance imports three years of history.<\/p>\n<p>Ask about concurrency: how many users can submit at the same moment on the last day of the month.<\/p>\n<p>Month-end is the honest test. Load the platform on a day when finance runs three reports and a hundred people approve.<\/p>\n<p>The limits on rows, API calls, file size and background jobs should be published in writing.<\/p>\n<p>Long-running calculations belong outside the platform, in a service that can be monitored and retried.<\/p>\n<p><a href=\"https:\/\/spacekits.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> gives a clean exit when the ceiling is reached: move the heavy logic behind an API and keep the interface.<\/p>\n<p>Design the data model for the volume expected in three years, not the pilot running this month.<\/p>\n<p>A slow app is worse than a paper form, because people trust the number and stop checking it.<\/p>\n<p>Monitor response time as an operational metric, with a threshold and a named owner when it is breached.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Shadow_IT_and_the_Spreadsheet_Estate\"><\/span>Shadow IT and the Spreadsheet Estate<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Most Kenyan mid-sized companies already run a low code estate made of spreadsheets and email.<\/p>\n<p>The stock report is a workbook with a macro, the debtor list is maintained by one person, and the payroll reconciliation lives on a laptop.<\/p>\n<p><a href=\"https:\/\/zamacore.com\">low code software development in Kenya<\/a> should inventory that estate before selling a platform. The spreadsheet is both the competitor and the requirement document.<\/p>\n<p>Each workbook is a process with hidden rules, and those rules are the valuable part.<\/p>\n<p>Interview the person who maintains it before looking at the formulas. They will describe the exceptions the sheet never shows.<\/p>\n<p>Rank the workbooks by the cost of an error, not by how often they are opened. The quiet one that feeds a statutory return matters most.<\/p>\n<p><a href=\"https:\/\/mystayorbit.com\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> can replace the worst five with a governed app, which often pays for the first year.<\/p>\n<p>Do not replace all of them. A monthly report that works is not a problem to solve.<\/p>\n<p><a href=\"https:\/\/dexa.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should give each spreadsheet a retirement date and a named successor process, or it will return.<\/p>\n<p>The risk in shadow IT is not the tool but the single person who understands it.<\/p>\n<p>Keep a written runbook for every workbook that survives the first cull, even the ones staying for another year.<\/p>\n<p>Ask what happens when that person goes on leave. The answer is usually a fortnight of silence.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Governance_and_Change_Control\"><\/span>Governance and Change Control<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>A low code app can be changed in an afternoon, and that is both the benefit and the risk.<\/p>\n<p>Without separate environments, a change made on Friday can break the month-end approval on Monday.<\/p>\n<p><a href=\"https:\/\/zama.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should separate development, testing and production, even when the platform makes it easy to skip.<\/p>\n<p>Every change needs a request, a reason, a tester and a release note. The form can be small, but it must exist.<\/p>\n<p>Batch changes into a weekly window. Continuous deployment suits a product team, not a finance department in its close.<\/p>\n<p>Freeze changes for the last three working days of the month. A release during close turns a small bug into a reconciliation problem.<\/p>\n<p><a href=\"https:\/\/pawa.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should record who approved the change and what was tested, because that is the first question after an incident.<\/p>\n<p>Version control is thinner in low code, so name releases and keep the export file.<\/p>\n<p><a href=\"https:\/\/pms.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should restrict production access to a small group, with a named deputy.<\/p>\n<p>Segregation of duties matters more, not less, when the builder is also the process owner.<\/p>\n<p>Keep a change calendar visible to the business, so nobody schedules a release on the day of a stock take.<\/p>\n<p>Review changes monthly with the business, and publish a short list of what went live.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"When_Custom_Code_Becomes_Cheaper\"><\/span>When Custom Code Becomes Cheaper<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Custom code wins when the logic is the product, when volume is high, or when the interface is the differentiator.<\/p>\n<p>A pricing engine with a hundred rules, a routing algorithm or a real-time integration deserves a codebase and a test suite.<\/p>\n<p>So does anything a regulator will inspect line by line, because the evidence has to be reproducible years later.<\/p>\n<p><a href=\"https:\/\/estateadmin.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should compare the annual licence with the cost of two developers and an environment.<\/p>\n<p>Custom code is not cheaper on day one. It is cheaper in year three if the process is stable and the volume is large.<\/p>\n<p><a href=\"https:\/\/churchesadmin.com\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should also weigh maintenance: a custom system needs a team, a roadmap and a security patch cycle.<\/p>\n<p>The hybrid is often right: low code for the forms and the queue, custom code for the calculation and the integration.<\/p>\n<p><a href=\"https:\/\/vega.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should define that boundary in writing, with data contracts between the two parts.<\/p>\n<p>Avoid rewriting a working app because the platform is unfashionable. Boredom is not a business case.<\/p>\n<p>Revisit the decision when the user count doubles or the transaction volume triples.<\/p>\n<p>Put the review date in the contract renewal diary, alongside the licence cost and the support fee.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Three-Year_Total_Cost\"><\/span>Three-Year Total Cost<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>The licence is the smallest line in most low code business cases, and the easiest to quote.<\/p>\n<p>Implementation, integration, training, support, governance and exit usually exceed it inside three years.<\/p>\n<p><a href=\"https:\/\/dereva.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should build the model with those lines visible, not buried inside a professional services estimate.<\/p>\n<p>Integration is usually underestimated. M-PESA, eTIMS, the ERP and the bank each need mapping, testing and monitoring.<\/p>\n<p>Add the cost of the people who will maintain those integrations, because the platform licence does not include them.<\/p>\n<p>Count the test environments too. Teams that test in production pay for it in incidents rather than in licences.<\/p>\n<p><a href=\"https:\/\/jaat.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should include internal time: the process owner, the tester, the trainer and whoever answers questions.<\/p>\n<p>Support is not optional. A business-critical app needs a rota, an escalation path and a named vendor contact.<\/p>\n<p>Price the premium support tier once. The difference between a four-hour and a four-day response is a real number.<\/p>\n<p>Add contingency for year two, when the first app has grown and the champion has moved.<\/p>\n<p>Compare the total with the process cost today: hours, errors, rework and the delay in closing the books.<\/p>\n<p>A business case that counts only licences is a quotation, not a case.<\/p>\n<p>Ask the finance manager to sign the assumptions, not only the total. The assumptions are what the board will question in year two.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Prototyping_Without_Committing\"><\/span>Prototyping Without Committing<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>A two-week prototype answers more questions than a six-month business case.<\/p>\n<p>Pick one process, use real data, and put it in front of the people who will use it every day.<\/p>\n<p>Record the session. What users say they need and what they do with the prototype are often two different requirements.<\/p>\n<p>Keep a list of what the prototype deliberately ignores. It becomes the scope document if the project proceeds.<\/p>\n<p><a href=\"https:\/\/wito.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should set exit criteria before the build: can a clerk finish the task in three minutes without help.<\/p>\n<p>Prototype the awkward part. If the approval chain has a delegate and a returning officer, build that, not the happy path.<\/p>\n<p><a href=\"https:\/\/awasam.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should be tested on the phones staff actually carry, on the network the branch actually has.<\/p>\n<p>A prototype is not a pilot. Do not put it into production because it worked in the meeting.<\/p>\n<p>Give the prototype an expiry date and delete it, or it becomes the system of record by accident.<\/p>\n<p><a href=\"https:\/\/saseni.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should document what the prototype proved and what it did not, with a decision date.<\/p>\n<p>Kill the idea early if the fit is poor. That is a successful prototype, not a failure.<\/p>\n<p>The output is a decision, not a demonstration.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Approvals_Audit_and_the_Finance_Sign-Off\"><\/span>Approvals, Audit and the Finance Sign-Off<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Finance cares about three things in any new system: who approved, what changed, and where the evidence sits.<\/p>\n<p>A workflow that sends a message and waits for a thumbs-up fails all three.<\/p>\n<p><a href=\"https:\/\/prim.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should capture the approver, the timestamp and the document, in a sequence that cannot be reordered.<\/p>\n<p>Delegation is normal in Kenyan organisations during leave and travel. Delegation must expire, and the delegate must be named.<\/p>\n<p>Test the delegation path while the approver is still in the office. A broken chain discovered in December is expensive.<\/p>\n<p><a href=\"https:\/\/rentaldesk.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should show the pending queue by approver, with an age in days, so nothing waits silently.<\/p>\n<p>The auditor will ask for a report of all approvals above a threshold. That report should exist before the request arrives.<\/p>\n<p><a href=\"https:\/\/fama.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should keep the history immutable, including rejected requests and their reasons.<\/p>\n<p>Sign-off by finance should be a step in the process, not an email after the fact.<\/p>\n<p>Report approval cycle time monthly. A queue that takes nine days is a process problem before it is a software problem.<\/p>\n<p>Name a single owner for the approval process, not a committee. Committees approve slowly and nobody is accountable.<\/p>\n<p>If the platform cannot prove who approved what, it is not ready for money.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Vendor_Lock-In_in_Practice\"><\/span>Vendor Lock-In in Practice<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Lock-in is rarely a single clause. It accumulates through skills, integrations and the shape of the data.<\/p>\n<p>The team learns the platform, the integrations are built to its model, and the data arrives in its format.<\/p>\n<p>Ask what a migration would cost if the price doubled tomorrow. If the answer is unknown, the negotiation is already lost.<\/p>\n<p><a href=\"https:\/\/spacekits.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should test the exit every year with a small export, not once at the end of the contract.<\/p>\n<p>Proprietary scripting is the subtle version. Logic written in the platform&#8217;s own language rarely moves anywhere.<\/p>\n<p><a href=\"https:\/\/zamacore.com\">low code software development in Kenya<\/a> should keep business rules in a documented table, so they can be re-implemented elsewhere.<\/p>\n<p>Ask for the roadmap and the deprecation policy. A platform that retires features will eventually retire yours.<\/p>\n<p>Negotiate a cap on renewal increases, or accept that the second negotiation is harder than the first.<\/p>\n<p>A short contract with a clear exit beats a long contract with a discount.<\/p>\n<p>Keep the source of any custom scripts in your own repository, even when the platform hosts the runtime.<\/p>\n<p>The goal is not to leave. It is to be able to leave, which changes the conversation.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Skills_Handover_and_the_Team_You_Keep\"><\/span>Skills, Handover and the Team You Keep<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Every low code programme depends on two or three people, and one of them usually leaves.<\/p>\n<p>The builder knows where the rules live, which is rarely where the documentation says.<\/p>\n<p><a href=\"https:\/\/mystayorbit.com\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should require documentation as a deliverable: data model, rules, integrations and the support path.<\/p>\n<p>Pair the builder with a second person from the business, and let that person release a small change alone.<\/p>\n<p>Rotate that second person every year. Two trained users are resilience; one is a risk with a nice title.<\/p>\n<p><a href=\"https:\/\/dexa.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should train a platform administrator who is not the vendor, and give that person production access.<\/p>\n<p>Handover is a rehearsal, not a document. Sit the new person in front of a live incident and watch.<\/p>\n<p><a href=\"https:\/\/zama.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should keep a skills map with names against each app, reviewed every quarter.<\/p>\n<p>Contractors are fine, but the knowledge should land inside the organisation.<\/p>\n<p>A platform with one expert is a single point of failure with a subscription attached.<\/p>\n<p>Write the handover into the job description, not into a goodbye email on the last Friday.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Integration_Depth_and_the_ERP_Boundary\"><\/span>Integration Depth and the ERP Boundary<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Low code is good at the edge and poor at the core. The ERP should remain the record for money and stock.<\/p>\n<p>An app that holds its own customer list will disagree with the ERP within a month.<\/p>\n<p><a href=\"https:\/\/pawa.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should read master data from the ERP and write transactions back, not the other way round.<\/p>\n<p>Idempotency matters. A retried webhook must not create a second payment or a second journal.<\/p>\n<p>Use the source document number as the key. Two systems that agree on the key can usually agree on the record.<\/p>\n<p>Replay one failed message by hand every month. It proves the error queue works before a real outage tests it.<\/p>\n<p><a href=\"https:\/\/pms.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should log every payload, with a status, a retry count and an owner for failures.<\/p>\n<p>Error queues need a screen, not an email inbox. Somebody should be able to see what is stuck.<\/p>\n<p><a href=\"https:\/\/estateadmin.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should define the contract: fields, formats, validation and behaviour on rejection.<\/p>\n<p>Batch and real time are different problems. Choose deliberately, then document the schedule.<\/p>\n<p>The boundary should be drawn in a diagram that a new developer can follow in ten minutes.<\/p>\n<p>Review the diagram when the ERP is upgraded, because an interface that worked last year can fail on a version change.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Security_Reviews_and_the_ODPC\"><\/span>Security Reviews and the ODPC<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>A low code app can hold personal data by lunchtime, and the obligations arrive with the first record.<\/p>\n<p>Registration as a data controller, a lawful basis and a retention rule apply to the app, not only to the core system.<\/p>\n<p><a href=\"https:\/\/churchesadmin.com\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should use single sign-on and multi-factor authentication, not a shared local password.<\/p>\n<p>Guest access and public links are the usual leak. Review every shared link and expire the ones nobody needs.<\/p>\n<p>Turn off anonymous access at the platform level, then allow exceptions with an owner and a date.<\/p>\n<p>Log every export of personal data, including the ones staff do for a report. Exports leave the building more often than records do.<\/p>\n<p>A data protection impact assessment should be recorded for anything touching health, finance or children.<\/p>\n<p>Vendor assessment is part of the review: where the data sits, who can see it, and what happens on a breach.<\/p>\n<p><a href=\"https:\/\/vega.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should test the restore and the deletion path before a regulator asks.<\/p>\n<p>Roles should follow the process rather than the org chart, and they should change when someone changes desk.<\/p>\n<p>A penetration test once a year is cheaper than the conversation after an incident.<\/p>\n<p>Track the findings to closure, with a severity and a date. A report nobody actions is a filing exercise.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Scaling_From_One_Department_to_a_Group\"><\/span>Scaling From One Department to a Group<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>The first app belongs to one department. The tenth belongs to a group with subsidiaries and a board.<\/p>\n<p>At that point the questions change from features to standards, and the answers change the budget.<\/p>\n<p><a href=\"https:\/\/dereva.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should introduce a platform team, a design standard and a review board before the estate doubles.<\/p>\n<p>Multi-entity data needs a clear rule: shared master data, separated transactions, consolidated reporting.<\/p>\n<p>Decide early whether the group wants one tenant or several. Moving later is a migration, not a setting.<\/p>\n<p>Agree which entity owns the contract and which entities consume it. Shared licences fail when a subsidiary is sold.<\/p>\n<p><a href=\"https:\/\/jaat.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should check the licence model across entities, because one subsidiary can change the bill.<\/p>\n<p>Naming conventions, colours, error messages and approval patterns should be consistent across apps.<\/p>\n<p><a href=\"https:\/\/wito.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should measure adoption by process, not by logins, or the dashboard will flatter the programme.<\/p>\n<p>A centre of excellence is a cost until it starts retiring apps and reusing components.<\/p>\n<p>Give it a target: five apps retired and three components reused in the first year, or the funding will be questioned.<\/p>\n<p>Scale the governance with the estate, not far ahead of it.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"The_Decision_Rule\"><\/span>The Decision Rule<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>The decision is not low code or custom code. It is which parts of a process deserve which tool.<\/p>\n<p>Start with transaction volume, the number of decisions, the regulatory exposure and the expected life of the process.<\/p>\n<p>Score the process against the platform shortlist. A tool that fits nine processes out of ten is still a tool with a gap.<\/p>\n<p><a href=\"https:\/\/awasam.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should be chosen for forms, queues, checklists and approvals that change every quarter.<\/p>\n<p>Choose custom code for pricing, statutory calculations, high-volume processing and anything that is the product itself.<\/p>\n<p><a href=\"https:\/\/saseni.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should keep the integration layer explicit, whatever the tool, so the boundary survives a platform change.<\/p>\n<p>Price the three-year total, including exit, and compare it with the process cost today.<\/p>\n<p><a href=\"https:\/\/prim.co.ke\" target=\"_blank\" rel=\"noopener\">low code software development in Kenya<\/a> should pilot with real users and a decision date, then retire whatever does not earn its place.<\/p>\n<p>Governance is the difference between a platform and a pile of apps.<\/p>\n<p>Review the estate every year against that rule, and be willing to close what no longer earns its place.<\/p>\n<p>The best outcome is a small estate that people trust, not a large one nobody can explain.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>low code software development in Kenya usually arrives through a finance team that has waited eight months for a small approval app. Someone discovers a platform,&#8230;<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,293,11,287,10,9],"tags":[],"class_list":["post-1139","post","type-post","status-publish","format-standard","hentry","category-ai-automation","category-academic-support","category-business-systems","category-product-guides","category-support-service","category-website-development"],"_links":{"self":[{"href":"https:\/\/zamacore.com\/blog\/wp-json\/wp\/v2\/posts\/1139","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/zamacore.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/zamacore.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/zamacore.com\/blog\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/zamacore.com\/blog\/wp-json\/wp\/v2\/comments?post=1139"}],"version-history":[{"count":1,"href":"https:\/\/zamacore.com\/blog\/wp-json\/wp\/v2\/posts\/1139\/revisions"}],"predecessor-version":[{"id":1144,"href":"https:\/\/zamacore.com\/blog\/wp-json\/wp\/v2\/posts\/1139\/revisions\/1144"}],"wp:attachment":[{"href":"https:\/\/zamacore.com\/blog\/wp-json\/wp\/v2\/media?parent=1139"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/zamacore.com\/blog\/wp-json\/wp\/v2\/categories?post=1139"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/zamacore.com\/blog\/wp-json\/wp\/v2\/tags?post=1139"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}