The update goes out before you ask for it
Nobody should have to chase a status. I prefer regular, clear updates, including when there is little movement, so people know where things stand rather than having to guess.
Abhishek KC
Associate Project Manager | Software Delivery & Client Coordination
hiitsmeabhishek11@gmail.com · linkedin.com/in/abhishek-kc4554 · Kathmandu, Nepal
I bring teams, client expectations and technical work together so projects keep moving, even when the plan changes.
About
Associate Project Manager · Software Delivery
My work sits between clients and the teams building their software. I help take projects from scoping and planning through development, QA, UAT and handover, keeping track of the dependencies, decisions and risks that can quietly move a delivery date. At Intuji, that includes client web and ecommerce projects, support and maintenance for 10 clients, and 10 ICT tender responses.
I work closely with engineering and QA on production-impacting changes, and I care about system behaviour, root causes and downstream impact rather than the ticket in front of me. I understand enough of the technical detail to ask the right questions, make the next step clear and keep the people involved working from the same picture.
That comes from years in customer experience and technical support, owning complex issues from intake to resolution. It still shapes how I approach delivery: I write updates people can act on, raise concerns while there is still room to respond, and keep expectations steady when a plan starts to change.
My strength is technical fluency and context building, not hands-on development.
How I work
Nobody should have to chase a status. I prefer regular, clear updates, including when there is little movement, so people know where things stand rather than having to guess.
A dependency slipping is easier to deal with when everyone knows early. I would rather raise an awkward concern while the team still has options than explain a missed date afterwards.
I want to understand what caused an issue and what else it might affect, not just whether the ticket can be closed. A fix that creates another problem further down the line is not much of a fix.
If support inherits a build nobody understands, the project may be live but the work is not really finished. Documentation and a proper handover belong in the delivery plan.
When teams and clients are in different time zones, a decision made on a call needs to be written somewhere useful. The next person should not have to wait for another meeting to find out what changed.
An estimate should reflect the work, assumptions and dependencies behind it. I would rather be clear about what fits than promise more and spend the next month explaining why it does not.
The work so far
At Intuji since Mar 2025 · 1 yr 9 mos in total, moving from client support into project delivery.
Run client delivery and support across engineering, QA, design and clients, keeping progress, dependencies and risk visible to everyone involved.
Transcription, data operations and AI annotation on financial documents, where the accuracy bar was absolute and the volume was high.
Data operations, AI annotation, quality assurance
Market research and outbound campaigns for a global employment platform, measured on replies rather than sends.
Apollo, market research, outbound campaigns
Client relationships handled live, and requirements pulled out of people who did not describe them in technical terms.
Client engagement, requirements facilitation, remote assistance
Front-line technical support and storefront quality for a consumer ecommerce business, since acquired by Deep Connection Technologies.
Website evaluation, CSS debugging, UX, developer collaboration
Where it started. Two and a half years of detail work across transcription, annotation and mapping, at the volume that teaches you what quality control is for.
AI annotation, geospatial mapping, quality assurance, project coordination
Toolkit
Writing
What I have learnt about support, project delivery and the parts of software work that tend to get overlooked.
A release path built around a tested rollback rather than a good night.
Triage, severity gates, and rebuilding a client’s trust in the status report.
Benchmarking the alternatives against real failed addresses, not a vendor demo set.
The requirements nobody writes down are the ones support inherits.
The gap between “it works” and “it keeps working” is where most tech projects actually live.
Understanding what is actually needed beats volume, effort, or the most elaborate solution.
Written follow-ups, consistent updates, plain language, and scope set early.
Contact
I am open to software project delivery, coordination and client implementation opportunities, including remote roles. I am also happy to hear about projects that could use someone to keep the moving parts together. Reach me by email, LinkedIn or the Let's talk button, and I reply within a business day.
WHAT IS IT ABOUT?
Nothing is stored or sent anywhere. Both buttons just open your own WhatsApp or mail app with the message ready.