We Don't Stop at a Proposal

Tomohiro Iida · Published June 23, 2026

Netsujo practices what we call implementation-led BizDev: rather than handing over a proposal and stepping back, we stay involved from structuring the concept through to building the technology ourselves. Why go as far as implementation? As a Kyoto-based startup, here is the honest reason we chose this stance.

This is not a how-to guide — it is a statement of our thinking. The definition of implementation-led BizDev itself, and how it works in practice, is covered in a separate article.

Key takeaways

Implementation-led BizDev is a way of running business development that carries a project from concept structuring through to technical implementation. The biggest difference from conventional consulting, which stops at a proposal, is whether you build it yourself.
Netsujo goes as far as implementation for three reasons: a concept only gets sharper once you start building; separating proposal from implementation causes failures; and we want to take responsibility all the way to the finished product.
Our experience running the engineer community "Miyako de IT" out of Kyoto since 2019 is part of the foundation for connecting concepts to real-world implementation.

01. What implementation-led BizDev means, briefly

Implementation-led BizDev is a way of running business development that covers concept structuring (a working session), technical verification, and development and implementation in one continuous flow. It does not stop at producing a proposal — it goes as far as something that works and gets used.

We cover the definition of the role and how it works in practice in a separate article. This article is only about why Netsujo chose this stance.

Covers the role of implementation-led BizDev, how it differs from sales or project management, and the practical steps.

Read: Implementation-Led BizDev — Role and Approach

02. How it differs from conventional consulting (comparison)

"What's different from consulting?" is the question we hear most. The two are not opposed to each other — they differ in scope of involvement and where responsibility ends.

Axis	Proposal/strategy consulting	Implementation-led BizDev
Final deliverable	A proposal or strategy document	A working product, a system in use
Scope of involvement	Through concept and strategy	From concept through technical verification, implementation, and operations design
How technology is handled	Feasibility is treated as a given	We work with it ourselves and prove it through a PoC
Scope of responsibility	Through delivery of the proposal	Through to something working and in operation
Best suited for	When the goal is mainly to organize direction or the market	When you want a partner who can be trusted through implementation

Neither is inherently better. Strategy-focused consulting suits work that is mainly about organizing direction; implementation-led BizDev suits it when you want to hand over the implementation itself.

03. Why we go as far as implementation

There are three reasons.

A concept only gets sharper once you start building: Discussion at the whiteboard tends to stall at "this looks feasible." Writing actual code, connecting it to outside services, and running something small surfaces the real issues. The further you go into implementation, the more concrete and honest the concept becomes.
Separating proposal from implementation causes failures: When the person who proposes and the person who builds are different people, you get proposals that cannot be implemented, or implementations that miss the intent. Carrying concept through to implementation with the same perspective removes the rework and ambiguity that separation creates.
Taking responsibility all the way to the finished product: Rather than stopping once the documents are delivered, we take responsibility through to something that works and gets used. We think that is what it means to act with integrity toward a business.

04. Kyoto, the place

Netsujo is based in Kyoto. Since 2019, we have run the engineer community "Miyako de IT" in Kyoto — study sessions and meetups, repeated over time, building a place where people and technology meet. That experience is part of the foundation of how we work today.

Running a community cannot be done through proposals alone. It is a continuous act of implementation: preparing a venue, bringing people together, and keeping it going. Moving first and testing it in the field, rather than only discussing it on paper, shows up directly in how we run business development.

05. What we value

Acting with integrity: Speak plainly, without exaggeration. Say honestly what we can and cannot do.
Building, not just commenting: Show it through implementation rather than commentary. Build something that works and verify it in the field.
Testing in small steps: Avoid betting everything at once. Verify a hypothesis through a PoC, with an exit criterion decided in advance.

Implementation-led BizDev is not a title — it is a stance. We do not separate the person who talks about the concept from the person who builds it. We take responsibility through to the working, used product that comes after the proposal. We believe that consistency is the greatest value we can offer our clients.

06. Where you can start

It's fine if the concept isn't settled yet. We can accompany you from whichever of the following three entry points matches where you are now.

From the stage where "there's something we want to do but it isn't defined yet," we help put the issues into words together.

Working session (structuring the concept)

We narrow down the hypothesis worth testing and build something small to check it, with an exit criterion decided in advance.

PoC (proof of concept)

For a business whose requirements are settled, we build it through to a working implementation.

Implementation and blockchain development

Frequently asked questions

What is implementation-led BizDev?: It is a way of running business development (BizDev) that carries a project from concept structuring (a working session) through technical verification and development and implementation, in one continuous flow. Unlike conventional consulting that stops at producing a proposal, it goes as far as something that works and gets used. We cover the role and approach in more detail in a separate article, "Implementation-Led BizDev — Role and Approach."
What is the difference from conventional consulting?: The main difference is whether you build the implementation yourself. When the person who proposes and the person who builds are different, misaligned intent and rework tend to follow. Implementation-led BizDev carries concept and implementation through with the same perspective, which reduces rework and sharpens the concept as you go.
Why is Netsujo based in Kyoto?: Netsujo is based in Kyoto and has run the engineer community "Miyako de IT" since 2019. Our experience building a place where people and technology meet in the region is part of the foundation for connecting concepts to real-world implementation.
What kind of company or business is implementation-led BizDev suited for?: It suits businesses in emerging areas such as Web3 or AI where there's something you want to do but no partner you can trust through implementation. We accompany you from a working session at the stage where the concept is not yet settled, or from a PoC when you want to verify something small.
Can we start by testing something small?: Yes. Rather than building something large right away, we place weight on narrowing the hypothesis worth testing and verifying it through a PoC. Deciding the exit criterion in advance means we can also value stopping when stopping is the right call.
From what stage can we start talking to you?: You can start from a working session while the concept is still unsettled. Whether you are putting an unformed idea into words, want to verify something small through a PoC, or have settled requirements and are ready to build, we accompany any of these entry points.
How much does it cost?: It depends on the stage and scale. To lower the uncertainty of commissioning work before you commit, Netsujo also offers fixed-price packages such as PoC design, a smart-contract pre-procurement audit, and an AI applicability assessment. See the pricing page or a free consultation for details.
Can you also support bringing the work in-house?: Yes. Beyond handling implementation on your behalf, we place weight on working alongside you in a way that leaves the knowledge in-house. We start by sorting out, together, what you keep in-house and what you hand over.

Summary

We practice implementation-led BizDev because we believe not separating concept from implementation is the most honest way to treat a business. The more you build, the sharper the concept gets, and the fewer the failures caused by separating proposal from implementation.

Running a community in Kyoto over the years, and continuing to improve our own site with our own tools, both come from the same root: build first, rather than only talk about it. That is the consistency Netsujo intends to keep.