a. Ankit Sigdel
KATHMANDU, NEPAL

ANKIT SIGDEL / FOUNDER, CODE PROS

I turn difficult ideas into technology that can survive the real world.

I’m Ankit, founder of Code Pros. I connect product thinking, software architecture, and the practical decisions that move complex systems into production.

INPUT → STRUCTURE → SYSTEM01—04
REQUIREMENTSPRODUCTENGINEERINGOPERATIONSFIG. 01 / RELATIONSHIPS, NOT ISOLATED PARTS
FROM CODE TO SYSTEMSProduct judgment. Engineering depth. Business reality.

01 / THE PROGRESSION

The work grew.
So did the responsibility.

A career shaped by the problems that came after the first working version.

01

I started by building interfaces.

Pages, WordPress, backend systems. Early work meant understanding the details, delivering directly to international clients, and learning how digital products are assembled.

02

The harder problems moved beyond the interface.

Architecture, data, infrastructure, users, budgets, and business models became part of the same problem. Writing the feature was no longer the whole answer.

03

So I built a company around solving them.

I founded Code Pros in Kathmandu in 2017. Independent delivery became a team effort: designing, building, operating, and improving substantial digital systems.

02 / WHERE I WORK NOW

Where business decisions
become technical systems.

01

Product direction

Turning incomplete ideas and business requirements into a product that can actually be designed, estimated, and built.

02

Technical architecture

Choosing structures, platforms, and infrastructure that fit the real constraints rather than the fashionable answer.

03

Team direction

Giving designers and engineers enough clarity to work as one team, with a shared understanding of the problem.

04

Client partnership

Working through tradeoffs, changing requirements, and the practical decisions that determine whether a system succeeds.

05

Long term execution

Supporting products when real traffic, data, integrations, and organisational reality begin testing the original decisions.

Close enough to the engineering to direct it responsibly. Far enough back to see the whole system.

03 / SELECTED WORK

Different contexts.
Connected thinking.

A selection of work through Code Pros.
Client identities kept private.

04 / THE COMPANY

Good systems are
a team effort.

code pros

KATHMANDU · EST. 2017 · WORKING GLOBALLY

Code Pros is how this work becomes bigger than one person.

I founded Code Pros for companies that need more than isolated development capacity. We bring product thinking and engineering together, from the first ambiguous requirement to the realities of ongoing operation.

We are most useful when the project contains uncertainty, connected systems, or decisions that cannot be solved by following a standard checklist.

  • Web applications & digital platforms
  • Data engineering & analytics
  • AI assisted products & workflows
  • Connected devices & IoT
  • Ecommerce & content infrastructure
  • Cloud architecture & ongoing operations
Get to know Code Pros ↗

05 / WORKING PRINCIPLES

A few things the work has taught me.

01

Start with the actual constraint.

The most visible problem is often not the problem determining the outcome.

02

Architecture is a business decision.

Every technical choice eventually appears as cost, speed, risk, flexibility, or operational burden.

03

A prototype should answer a question.

Building faster has little value when nobody has defined what the build is supposed to prove.

04

Complexity does not disappear.

It can only be understood, moved, reduced, or hidden from the wrong person.

05

Production changes the conversation.

Real users, incomplete data, integrations, and maintenance reveal what the original plan ignored.

06

Technology should earn its place.

Do not add AI, automation, or new infrastructure merely because it is available.

06 / THE PERSON BEHIND THE WORK

Still curious.
Just asking bigger questions.

I began as a developer and independent freelancer in Nepal. Over time, clients started relying on me for more than code: understanding their businesses, shaping their products, and helping teams make decisions that would last.

Today, I spend less time trying to write every line and more time making sure the right problem is understood, the right system is chosen, and the team can execute it well.

More about my journey ↗

07 / NOTES FROM THE WORK

Room for considered thinking.

On building a technology company, technical tradeoffs, and what happens after launch.

Visit the notebook ↗

08 / CONTINUE THE CONVERSATION

What are you
working through?