Inherit, stabilise and keep running software someone else built. Bug fixes, upgrades, cloud costs, and an honest assessment of what you actually have.
Software that already exists and has to keep working is a different job from building something new, and plenty of developers dislike it. I do not.
The first deliverable is an assessment, not a commitment: what you have, what is fragile, and what keeping it running actually costs. Sometimes that assessment says you do not need a retainer, and I will tell you so.
What the code does, what is fragile, and what it would cost to keep versus replace - written down, in plain language.
The fix, and what let it happen. A patched symptom comes back.
Framework versions, deprecated APIs, expiring credentials - the work that is invisible until it is an outage.
Most inherited systems are paying for something nobody uses.
A runbook that grows while I work, so the next person does not start where I started.
Code, infrastructure, and whatever the last person left behind. You get the assessment before committing to ongoing work.
Backups, monitoring and outstanding security updates come before features.
Driven by what is costing you time or money, not by what is most interesting to fix.
Completely normal, and it is most of what a takeover is. Reading unfamiliar code is a skill in itself, and I am not put off by it.
Almost never. A rewrite is usually a developer preferring their own code to reading someone else's. Sometimes one component genuinely has to go, and I will make that case specifically rather than sweepingly.
An agreed block of hours a month covering fixes, upgrades and small changes, with what was spent reported. Unused hours are not a windfall - if you consistently do not need them, we lower the block.
A fair question to ask anyone who takes this on. Everything lives in your repository, deploys from your accounts, and the runbook is kept current, so another developer can pick it up. That is a deliberate property, not a courtesy.
Retrieval-augmented AI that answers from your documents and cites the page it used, or says it does not know. Built and run in production, not a demo.
Connect the systems your business already runs and automate the work in between. WhatsApp Business API, Stripe, Twilio, QuickBooks, Airtable and Google Workspace.
Move your data somewhere it can be asked questions, and build the dashboards on top. BigQuery, dbt, Airflow, Power BI and Looker Studio, shipped for clients since 2019.
The work behind these is public: the AI product, its live demo, the cited answer pages it produces, and the research paper measuring it.
Send a short brief — what you need built, roughly when, and the budget you have in mind. You'll get a reply from Muhammad Kashif Irshad himself, in writing, within one working day, saying plainly whether this is a good fit.
