Skip to main content
METHODOLOGY & ARCHITECTURAL DISCIPLINE

How I Work

Seven things I do and how each one actually runs: WordPress builds, system design, automation, search, brand, mentoring and business tools setup.

THE CRAFT

WordPress, Any Way You Need It

Figma file, template, existing site, or blank folder. Custom themes and plugins from scratch, page builders when speed wins, customisation when that fits.

PHP
WordPress
Themes
Plugins
Builders
Figma
THE SYSTEM

SaaS System Design and Architecture

Data models, roles, permissions, structure, integrations. I work out how SaaS products and internal platforms hold together, then stay through the build.

Design
SaaS
Data
APIs
MySQL
Next.js
THE ENGINE

Automation and AI

Some work should never be manual twice. Processes mapped, the right tool chosen, systems connected through their APIs, and AI used only where it genuinely pays.

Automate
APIs
AI Core
Webhooks
Mapping
THE REACH

Digital Marketing and Search

A site nobody finds is an expensive brochure. Technical SEO, GEO and AEO for AI answers, paid campaigns on Google, Bing and Meta, and proper measurement.

SEO
GEO/AEO
Google
Bing
Meta
GA4
THE VISION

Brand and Creative Direction

People decide whether to trust you before reading a word. Logo and brand identity, creative imagery for web and campaigns, video for launches, ads and social.

Logo
Identity
Imagery
Video
Assets
THE STANDARD

Mentoring and Team Guidance

Explain it clearly, then let them do it. Theme and plugin development, front end standards, code review, Git workflow, documentation someone else can follow.

Review
Standards
Git Flow
Docs
Onboard
THE FOUNDATION

Business Tools and Setup

The software your business quietly runs on. Email and identity, CRM and pipeline, projects and communication. Advice first, then setup, connection, handover.

M365
Google
HubSpot
ClickUp
Slack

Projects don’t usually fail technically; they fail when direction is unclear and knowledge disappears.

HOW I WORK

No surprises. That is the whole method.

01
STEP 01
WEEK 1

Scope, architecture, and
written agreement.

Before a single line of code is written, we define data models, technical constraints, integration contracts, and what done looks like. No assumptions, no scope creep.

Technical Architecture Document (TAD)
Fixed milestones and deliverable checklist
02
STEP 02
WEEKS 2–4

Build in public, weekly
working previews.

You never wait six weeks to see what is happening. Private staging link updated on every sprint. You click around, test features as they land, and give feedback in real time.

Private staging with password protection
Asynchronous video walkthroughs on progress
03
STEP 03
WEEK 5

Testing, performance audits,
and launch.

Cross-browser verification, Core Web Vitals profiling, security hardening, automated backup verification, and smooth zero-downtime DNS cutover.

95+ Lighthouse score across all categories
SSL, Cloudflare edge caching, and firewall set up
04
STEP 04
WEEK 6 & BEYOND

Handover, documentation, and
zero lock-in.

Every credential transferred. Clean Git repo with complete README. Custom video tutorials recorded for your team. You own everything outright — no recurring dependencies on me unless you want ongoing support.

Complete documentation and recorded videos
Git repository handover with clean history

Nothing here is unusual. It is just done in order, every time, which turns out to be the difference.

NBK
ABOUT

Namaste, properly this time.

Nirajan

Nirajan

WEB ENGINEER

Web engineer, eight years in. Custom WordPress, system architecture, and the marketing and automation that keeps it all running. Kathmandu based, working across five countries.