{"version":"1.0","provider_name":"Graph Technologies","provider_url":"https:\/\/graph.co.ke\/blog","author_name":"GraphAdmin","author_url":"https:\/\/graph.co.ke\/blog\/author\/graphadmin\/","title":"Engagement Principles - Graph Technologies","type":"rich","width":600,"height":338,"html":"<blockquote class=\"wp-embedded-content\" data-secret=\"UxH7ufUhlY\"><a href=\"https:\/\/graph.co.ke\/blog\/engagement-principles\/\">Engagement Principles<\/a><\/blockquote><iframe sandbox=\"allow-scripts\" security=\"restricted\" src=\"https:\/\/graph.co.ke\/blog\/engagement-principles\/embed\/#?secret=UxH7ufUhlY\" width=\"600\" height=\"338\" title=\"&#8220;Engagement Principles&#8221; &#8212; Graph Technologies\" data-secret=\"UxH7ufUhlY\" frameborder=\"0\" marginwidth=\"0\" marginheight=\"0\" scrolling=\"no\" class=\"wp-embedded-content\"><\/iframe><script>\n\/*! This file is auto-generated *\/\n!function(d,l){\"use strict\";l.querySelector&&d.addEventListener&&\"undefined\"!=typeof URL&&(d.wp=d.wp||{},d.wp.receiveEmbedMessage||(d.wp.receiveEmbedMessage=function(e){var t=e.data;if((t||t.secret||t.message||t.value)&&!\/[^a-zA-Z0-9]\/.test(t.secret)){for(var s,r,n,a=l.querySelectorAll('iframe[data-secret=\"'+t.secret+'\"]'),o=l.querySelectorAll('blockquote[data-secret=\"'+t.secret+'\"]'),c=new RegExp(\"^https?:$\",\"i\"),i=0;i<o.length;i++)o[i].style.display=\"none\";for(i=0;i<a.length;i++)s=a[i],e.source===s.contentWindow&&(s.removeAttribute(\"style\"),\"height\"===t.message?(1e3<(r=parseInt(t.value,10))?r=1e3:~~r<200&&(r=200),s.height=r):\"link\"===t.message&&(r=new URL(s.getAttribute(\"src\")),n=new URL(t.value),c.test(n.protocol))&&n.host===r.host&&l.activeElement===s&&(d.top.location.href=t.value))}},d.addEventListener(\"message\",d.wp.receiveEmbedMessage,!1),l.addEventListener(\"DOMContentLoaded\",function(){for(var e,t,s=l.querySelectorAll(\"iframe.wp-embedded-content\"),r=0;r<s.length;r++)(t=(e=s[r]).getAttribute(\"data-secret\"))||(t=Math.random().toString(36).substring(2,12),e.src+=\"#?secret=\"+t,e.setAttribute(\"data-secret\",t)),e.contentWindow.postMessage({message:\"ready\",secret:t},\"*\")},!1)))}(window,document);\n\/\/# sourceURL=https:\/\/graph.co.ke\/blog\/wp-includes\/js\/wp-embed.min.js\n<\/script>\n","description":"How We Choose What to Build \u2014 And Why At Graph Technologies, we do not accept every project. This is intentional. Our engagement principles exist to protect: This page outlines the conditions under which we engage\u2014and the situations where we intentionally decline. Our Core Principle We build durable systems, not disposable software. If a project cannot be owned, explained, governed, or maintained responsibly, we do not proceed\u2014regardless of budget or urgency. What We Will Not Build 1. AI Without a Clear Decision Problem We do not build AI systems unless there is a clearly defined operational decision being improved. If the problem can be solved reliably with automation or rules, we will recommend that instead. Why:AI without decision clarity creates risk, not value. 2. Systems Built on Ownerless or Unreliable Data We decline projects where: Why:No model compensates for broken data foundations. 3. Software That Cannot Be Owned Internally We do not build systems that: Why:Software must be an organizational asset, not a permanent external liability. 4. \u201cCheap\u201d Builds With Predictable Long-Term Damage If a project requires skipping: We will decline or re-scope. Why:Short-term savings that create rebuild cycles are not cost-effective\u2014they are wasteful. 5. Systems That Ignore Regulatory or Ethical Responsibility We do not engage in projects that: Why:Engineering responsibility is not optional, especially in regulated environments. 6. Architectures With Undefined Failure Modes If a system is expected to: We will stop and redesign\u2014or decline. Why:Enterprise systems must fail predictably and recover gracefully. 7. Hype-Driven or Trend-Chasing Projects We do not build products driven primarily by: Why:Trends fade. Systems remain. What We Do Say Yes To We actively engage in projects that: These projects may take longer to define\u2014but they succeed far more often. What This Means for Clients Our engagement principles: A partner who never says no is a vendor.A partner who sets boundaries is accountable. How Engagement Typically Begins This protects both sides. Final Note These principles are not restrictive.They are protective. They allow us to focus our time and expertise on work that compounds value\u2014technically, operationally, and ethically. If these principles align with how you think about software, we are likely a good fit.","thumbnail_url":"https:\/\/media.geeksforgeeks.org\/wp-content\/uploads\/20200613135536\/Untitled269.png"}