Hi — I'm Aseem Kishore.
I run AK Internet Consulting from Maryland. I help small businesses and content teams keep WordPress sites stable, fast, and secure — and I build automations (often with AI) that eliminate repetitive work.
If your site is "mostly fine" but you're constantly dealing with:
- plugin update anxiety
- random performance slowdowns
- security concerns
- messy workflows and manual busywork
…that's the stuff I fix and prevent.
What I do (in plain English)
1) WordPress maintenance & troubleshooting
I keep sites online and boring (in the best way). That includes:
- Core/theme/plugin updates (with a staging-first mindset when possible)
- Backups + restore plans
- Malware cleanup + hardening
- Performance tuning (caching, image optimization, plugin audits)
- Small fixes and "why is this broken?" troubleshooting
If you want the fuller scope, that's basically what my Care Plans are built around.
2) Automation building (with or without AI)
If you're doing the same task every week, you're paying a "repetition tax."
I build custom automations using n8n, Zapier, Make, or direct API integrations — whatever fits your setup and budget. Typical examples:
- form submissions → CRM/Google Sheets/Notion
- Slack/email alerts when something changes
- scheduled reports and dashboards
- email triage, labeling, routing, and attachment handling
- AI-assisted workflows (summaries, draft generation, classification, enrichment)
I'm not a tool pusher. Sometimes the best solution is Zapier. Sometimes it's a simple script on a schedule. Sometimes it's an n8n workflow you own.
Why I'm qualified to touch your production site
I didn't start as a "freelancer." I started as the person responsible when things broke.
I began in IT, then started my first tech blog in 2007 while working as a network administrator. What began as "writing down the fixes so I'd remember them" turned into a network of WordPress sites that reaches millions of readers. Over the years I've dealt with the real stuff: plugin conflicts, hacked sites, broken updates, slow pages, messy migrations, and the constant maintenance grind.
At one point I wrote thousands of articles myself before going full-time — which taught me something that's still true today:
Systems beat heroics.
These days I spend less time writing and more time building the systems that keep sites and teams running: maintenance workflows, automation pipelines, dashboards, and integrations.
Sites I've built and operate
These are the core sites in my network:
Running multiple sites forces you to get good at reliability, repeatable processes, and fixing problems fast — because downtime is expensive.
Recent work (examples)
A few projects that reflect the kind of work I do for clients:
Financial Portfolio Dashboard
A real-time dashboard with serverless API routes, live polling, uploads, and monitoring — built to pull multiple data sources into one place.
SEC Filing Monitor
An automated pipeline that checks EDGAR, summarizes new filings using Claude, and sends alerts — built with scheduled workflows and API integrations.
AI Content Pipeline (WordPress)
A multi-stage workflow that goes from topic discovery → research → drafting → screenshots → publishing drafts to WordPress.
(Some repos are private because they touch business data, but I'm happy to talk through details.)
How I work
Practical, not theoretical
I recommend what I've used in production — because I've had to live with the consequences.
Clear communication
No jargon, no mystery. I'll tell you what's wrong, what it'll take to fix, and what the tradeoffs are.
Handoff-ready
I document everything: what I changed, why, and how it works — so you're not locked into me.
A typical project flow
- 1Quick discovery — what's broken, what "done" looks like, what constraints exist
- 2Plan — fixes first, then improvements, then optional upgrades
- 3Build + test — ideally with staging, backups, and rollback options
- 4Deploy + monitor — confirm impact and catch edge cases
- 5Handoff — notes, walkthrough, and next-step recommendations
Tools I'm comfortable with
This depends on the project, but common tools include:
- WordPress (core, themes, plugins), WP REST API, performance + security tooling
- n8n / Zapier / Make, webhooks, REST APIs
- Google Workspace, Slack/Discord, Airtable/Notion
- GitHub + GitHub Actions for scheduled workflows and automations
- Node.js/Python scripts when "automation platform" isn't the right fit
- Vercel/serverless patterns for lightweight apps and dashboards
If you already have a stack, I'll work inside it. If you don't, I'll recommend something maintainable.
Want to work together?
If you have a WordPress site that needs consistent maintenance (or a workflow you're tired of doing manually), reach out and tell me what you're dealing with.
Get in Touch