Services
Engineering-first ServiceNow work. I focus on solutions that are observable, maintainable, and fast enough to stay fast.
Engagement packages (no fluff)
Integration Health Check
Good for: unstable integrations, unclear failures, fragile auth and retries.
Output: risk list, concrete fixes, logging and retry plan.
What I need: access to integration configs, logs, and a couple of real examples.
Performance Triage
Good for: slow forms, slow lists, heavy background jobs, “why is this spiking”.
Output: top bottlenecks, quick wins, measured before/after, prevention steps.
What I need: a few problem scenarios, instance access, and performance data where available.
Platform Code Baseline
Good for: copy-paste code, unclear ownership, and patterns that drift over time.
Output: reusable utilities, conventions, and a structure that teams can extend safely.
What I need: your current approach, key modules, and the constraints you live with.
1. Integrations
REST, SOAP, MID Server, auth, retries, and logging.
- Integration design that survives real traffic and real failures.
- Retry strategy, idempotency, and clear error handling.
- Tracing and logs that make support work boring.
2. Platform engineering
Script Includes, reusable libraries, and governance.
- Shared utilities and patterns that reduce copy-paste.
- Guardrails: naming, conventions, reviewable structure.
- Documentation that matches the code and the data model.
3. Performance
PA, query tuning, indexes, and async/event patterns.
- Find the real bottleneck (queries, client calls, or architecture).
- Fix with measured impact and low regression risk.
- Make “fast” the default, not a special mode.
4. AI & AI add-ons
Knowledge agents, translation, logging, guardrails.
- Integrate with internal or external LLMs via a replaceable layer.
- Usage logging and safety patterns suitable for enterprise.
- Start small, reuse the foundation, scale by demand.
5. Portal and Workspace
Widgets, UI performance, and maintainability.
- Reduce server calls and client overhead.
- Make changes safe to extend across teams and releases.
- Keep UX clean without hiding technical realities.
How engagements typically work
- Quick call: goals, constraints, and current state.
- Technical plan: concrete steps and trade-offs.
- Delivery: implement, log, test, document.
- Handover: clean ownership and a runbook if needed.