[Venture Ecosystem Case Study] “One Tech World”: Results from Year 1
Hello, this is Kazuhiro Maekawa from techbeans inc.
On November 27, 2025, we stood at our booth at the DXPO exhibition. It was the first exhibition where all three companies—techbeans inc., atmark Solutions Co., Ltd., and idealump Co., Ltd—exhibited together. To be honest, we felt good about it, but the number of companies we met over the two days was only about half of our target, and not a single one of those encounters led to any business in the end.
Fast forward nine months to August 2026 at Tokyo Big Sight. Sales and non-engineering members called out to people passing by the booth, while engineers handled the technical discussions with those who stopped. Over these two days, by dividing roles across the companies, the number of businesses we connected with significantly surpassed our previous attempt, and the number of companies moving on to business negotiations surged.
techbeans, atmark Solutions, and idealump: in my previous article, [Venture Ecosystem Case Study] The Power of Three Arrows, I previously wrote about how these three IT company members of D-POPS GROUP formed the development alliance “One Tech World” as three arrows bundled together.
One year has passed since then. What happened to the four challenges we outlined last time? I’d like to reflect on this past year of operating as a united front, sharing both our successes and our setbacks.
To get straight to the point, just bringing three companies together wasn’t enough. Each has its own management policies and internal circumstances, so the real challenge lay in figuring out exactly how to bundle the arrows. Creating synergy was no easy task. So, how did we tackle this? Let me walk you through, aligning with the four challenges we established in our previous article.
1. The Results: What Happened with Our Four Challenges
Accelerating Development with AI
We held regular meetings with the development leaders of all three companies, bringing our AI knowledge to the table for ongoing discussions. We developed design document templates, prototyped diagnostic tools to measure AI utilization, and created systems to visualize how AI coding tools are being used. Each company also kept moving forward on their own in various ways, such as by appointing AI evangelists, distributing tools to all engineers, and providing premium AI plans to members developing upstream processes.
However, rolling out AI-driven development methods to all engineers on the ground across the three companies was a series of trial and error. AI keeps evolving day after day, month after month. A top-down approach dictating the best way to use it would become outdated in just three months, while the frontline engineers were already utilizing newer methods. Furthermore, there were differences in perspective among the companies.
Therefore, instead of forcing a standard operating procedure from the top, we institutionalized a bottom-up approach where all members bring the knowledge and practices they pick up from working on the ground, and share it. We asked the people actively using AI in their projects to present their everyday workflows just as they are and openly exchange opinions.
On November 13, we will host an “AI Sharing Session” where we’ll hear from two currently dispatched members from each of our three companies. It’ll be an opportunity for senior, mid-level, and junior staff—not executives—to learn how peers at their own level are using these tools. When executives speak, it often ends with people thinking, “Well, only people like them can do that,” and it’s difficult for them to relate. Instead, we want an environment where rather than searching for a single “best” answer, everyone increases their know-how both by figuring it out themselves, and also by refining their skills through listening to others in the group. This process results in building a shared understanding of our goals.
Driving Inbound Traffic Through IdeaLamp’s Creativity
In August 2026, we launched a cross-company web development service on a website called “Web Dev Navi”. Over a dozen engineers from our three companies are featured with their names and faces, and the site highlights a free prototyping service called “Zero Start”. idealump handled the design, atmark Solutions took care of the implementation, and techbeans oversaw the overall direction. We are working on improving our response to the inquiries this site generates.
[Web Dev Navi] (website in Japanese only)
Web Dev Navi provides free consultations with skilled, senior developers. They promise not to push anyone to pay for a project and not to dishonestly claim they can do something that they really can’t.
Tackling Major Projects with a Streamlined Production System
In July of this year, the representatives of all three companies formed a united front to handle negotiations with a major manufacturer. We have progressed to signing a non-disclosure agreement and are currently in the detailed analysis phase. In another instance, a company handling M&A in the IT sector praised our very structure, appreciating that they could entrust everything to us as a unified entity, from infrastructure and applications to upstream processes. We are making steady progress, but there are still many hurdles to overcome. The real breakthrough is yet to come.
Bringing in Partner Companies from Outside the Group
In February 2026, we welcomed partners like AmpTech and Beekle, who were willing to sign non-disclosure agreements with all three of our companies. We have set up exhibitions alongside AmpTech twice, and now we’ve asked them to handle the DX projects that are landed by One Tech World. Beekle not only introduces projects to us but also shares their deep AI expertise, and we are currently creating a space for us to exchange knowledge on a regular basis. This is one example where we can say we successfully met the challenge.
Let’s take a quick look at the numbers behind what we generated over this past year:・We connected with a total of 126 companies between the two exhibitions. We moved forward to business negotiations with about 25 of them, and just before I finished writing this article, we secured our first order from one of those companies.・We launched a cross-company website featuring the names and faces of over a dozen engineers.・With the addition of partners outside the group, our internal collaborative projects increased from our previous benchmark (20 or more projects) to 40–50 projects annually.・Furthermore, among the projects secured by the three companies, continuous monthly contracts grew by approximately 1.5 times on a monthly recurring basis from spring to autumn.
Diligently tracking these quantitative metrics is crucial.
2. The Source of Our Projects
Naturally, simply holding a joint exhibition wasn’t a magic wand for easily securing contracts.
So, where did those contracts come from? They didn’t come from attending the exhibition, but rather from increasing our ability to take on projects as a three-company team.
One of techbeans’ long-standing clients is a company that supports e-commerce (EC) web development. We’ve been receiving a stream of EC development contracts from them. Truthfully, techbeans wouldn’t be able to handle that volume alone. So, we proposed a solution together with idealump and successfully secured the order. Today, idealump handles everything from construction to maintenance. Even if it comes through one company, the company best suited for the task takes the lead. The fundamental model of our alliance has transitioned from a hopeful dream into actual workflows. A year in, a natural rhythm has taken shape: atmark Solutions handles infrastructure and maintenance through monthly contracts, while idealump takes on EC development on a project-by-project basis.
Here is another example. This autumn, we completed a DX project where a business consulting firm visualized the workflow, and our alliance partner AmpTech handled the development. The prime contractor gave us phenomenal feedback, saying it was extremely good. Our style is to visualize the end goal, form a consensus, and then build small while confirming each step. For us, the best possible response would be for people to say, “One Tech World is the go-to for proofs of concept.”
And this is the most significant change over the past year: we have shifted from hunting down individual companies at exhibitions to establishing a continuous influx of projects. We formed sales partnerships with business consulting firms and EC development support companies, allowing One Tech World to take on the projects they generate. The consulting firm receives about 10 inquiries a month, with development kicking off a few months after they visualize the project. Instead of chasing one-off orders, our very entry point is transforming into a system where the three companies continuously absorb incoming project flows. We expect this to gain serious momentum by early 2027.
In D-POPS GROUP’s article “Venture Ecosystem: A Platform for Growth and Sustainability”, we see that “pioneering customers” and “industrial cooperation” are key elements of collaboration. Over this past year, these are the two areas where we have consistently delivered concrete results.
3. What Changed Through Group Collaboration
From techbeans’ perspective, the transformation is very apparent: we are now able to sit at negotiation tables that we could never have reached alone. When you combine idealump’s UI/UX expertise with the infrastructure capabilities of atmark Solutions, an AWS partner, the depth of our proposals is completely different. The only reason we could confidently enter negotiations with a major manufacturer alongside all three company representatives, or jointly propose in-house development support for a major retail chain with atmark Solutions, is precisely because of this combined strength.
There is one more thing. When techbeans was short on hands for a large-scale project, engineers from the other two companies stepped in to help. We can support each other when resources are tight. This was the benefit from our group collaboration that I personally felt most strongly.
So, what role does techbeans play? What we are doing now is handling everything from defining requirements to developing business systems, while consistently building up development efficiency and quality improvements using AI across our daily projects. We analyze what each client wants, determine what to entrust to AI, decide what humans need to design, and establish where to insert reviews. I believe techbeans’ role among the three companies is to establish this workflow as the standard for One Tech World, and to lead the way in raising up forward-deployed engineers (FDEs), which I will explain in Section 4.
atmark Solutions’ infrastructure and security capabilities serve as an important foundation for our joint proposals. Having a company on the same team that can be trusted with everything from cloud design to operations completely changes the level of assurance our clients feel.
idealump’s President Miyahara reflected on this past year as follows:
“We are now able to offer one-stop proposals that include areas like core system integration and infrastructure—areas where our proposal scope was previously limited on our own. Particularly in proposals for e-commerce website renewals, AX (AI Transformation), and DX support, collaborating with each company right from the proposal stage has led directly to orders and highly viable pitches. Combining the technologies of our three companies this past year has truly increased our likelihood of winning contracts.”
4. Where We Stumbled
Not Adequately Pursuing Prospective Clients
Regarding the companies we met at our first exhibition, we simply couldn’t follow up on every single one. Some projects couldn’t move forward due to budget mismatches, while in other cases, we simply stopped receiving replies. However, in order to properly chase those leads, we simply didn’t have the manpower.
For the second exhibition, we decided on just one rule: if we send two emails and get no response, we call them. That’s it. A solid 38.5% of the companies we called moved forward to business negotiations. And for the record, not once did anyone get angry at us.
Ultimately, one of those negotiations turned into our very first order from an exhibition right at the end of One Tech World’s first year together.
For anyone coming from a sales background, this is probably elementary, but we all work at systems companies, and hardly any of us had accumulated any deep sales knowledge. So, for that precise reason, we documented our actions in standard operating procedures, rolled them out as a shared method across all exhibiting companies, and applied them consistently to every lead. The true value lies in taking this sales model we built from scratch and making it an asset of the alliance, rather than an asset of any single company. Starting with the next exhibition in November, we will operate using this exact method.
How to Build a Track Record Without a Track Record
This happened when we pitched to an IT company within a major development conglomerate: they acknowledged our technical capabilities, but we didn’t end up landing the contract. Why? They told us, “You lack a track record of delivering results as a unified team.” In another project for a listed company group, the decision-maker’s anxiety surrounding AI-driven development was a contributing factor in losing the deal.
It is frustrating, but the takeaways are crystal clear. If we are going to tout our ability to handle large-scale projects, we first need to build a track record as a three-company team on mid-scale projects. Furthermore, when it comes to AI, we cannot just say, “We work fast.” We have to clearly convey that while man-hours are reduced, documentation and testing remain thorough, preventing operations from becoming overly dependent on specific individuals. Only when we present that sense of security as a package deal will decision-makers agree to hire us.
Fighting Fragmented Battles
This was the most painful issue. All three companies were busy running their own individual projects without bothering to find out which members in the neighboring companies were available. We were supposed to be bundled together, yet we remained scattered.
The one who gave us the push we needed was D-POPS GROUP’s Managing Executive Officer Watanabe. “Because you aren’t visualizing, each company ends up fighting your battles alone.” Inspired by these words, we took the leap to visualize our resources and established the rule that any leads generated through the exhibition belong jointly to our alliance. We were also greatly aided by Officer Watanabe’s advice, “It doesn’t matter if it’s small, just start.”
Following those words, we built the framework ourselves. While it might seem like stating the obvious, we realized that pushing forward earnestly, steadily, and persistently is more important than anything else. Just creating tools by itself is an empty process. It is equally critical to assign a dedicated person to drive it forward and to hold regular meetings, even if time is scarce. We are now working to systematize these elements as a cohesive whole.
“Knowing the Client” is Also Part of an Engineer’s Job
We learned one more thing from the high praise we received on the DX project mentioned earlier. Client satisfaction is not determined solely by the quality of the final deliverable. It is the attitude of immersing oneself in the client’s challenges and business, stacking up mutual understanding and thorough communication, and tackling those issues together with the client. This is the differentiator that dictates the final evaluation.
“Knowing the client.” It is the absolute bedrock of business. People often think this is strictly the realm of sales, but we believe it’s a skill that engineering professionals must also master. Code written without knowing the client and code written with a deep understanding of the client yield totally different levels of quality, even under the exact same specifications. We want our standard of quality to be the product of our technical capability multiplied by our ability to understand the client’s needs.
Engineers who really dive into the project with their clients and provide hands-on support from discovering problems right through to reaching the solution are known overseas as “forward-deployed engineers” (FDEs). This concept is starting to become more commonplace in Japanese companies, as well. We are making it one of One Tech World’s core policies to cultivate FDEs in our companies.
5. How Far Have We Come Within the Venture Ecosystem?
The earlier-mentioned article about our Venture Ecosystem lists collaboration (pioneering customers, industrial cooperation, personnel exchange, and generating new business) and mutual learning and support (study groups, lending and transfers, and joint recruiting activities) as foundational elements supporting the Ecosystem.
As I’ve described so far, pioneering customers and industrial cooperation have begun to materialize with real projects. Personnel exchange is also gradually taking shape in the form of jointly running exhibition booths and engineers participating in projects across companies. In terms of generating new business, initiatives like Web Dev Navi, Zero Start, and our system for integrating the skill sheets of employees across our three companies have started to take off.
On the other hand, we are still laying the groundwork for mutual learning and support. Our study groups are only starting to grow from simple knowledge sharing among development leaders to sharing sessions where frontline members take the stage. As for lending, transfers, and joint recruiting activities, we will figure out how to utilize those cross-company human resources moving forward.
The fact that we achieved some things and have yet to achieve others is a perfect reflection of our first year together.
6. Next: Bundling Our Arrows Together Even More Tightly
We have four objectives for the coming year.
First, to raise up FDEs by putting together an ability to master AI with an ability to know the client. We won’t let November’s AI Sharing Session end as a one-off event; we will continue it as a forum for bringing real-world applications to the table. By doing so, we will forge a shared understanding across the three companies while multiplying the number of engineers who can dive into client challenges and provide end-to-end support until a resolution is reached.
Second, to utilize cross-company talent. Implementing, visualizing, and sharing human resources has been a challenge since One Tech World was formed. Using a clear picture of our operational capacity as a starting point, we will secure projects as a team and proactively seek out collaborative efforts where engineers from all three companies operate seamlessly across corporate borders.
Third, to build a solid track record as a three-company team. To break out of the awkward situation of not being able to build a track record because we lack a track record, we will initiate joint proposals and form teams across the three companies. The major manufacturer project currently underway will serve as a starting point for this.
Fourth, to increase the number of companies we can serve as much as possible. It took a full year to finally land a single contract from our exhibitions. We expect Web Dev Navi to generate some inquiries, and we will enter the exhibitions in November 2026 and January 2027 armed with the sales framework we built from the ground up.
And beyond that, we want to become the epicenter of IT synergy within D-POPS GROUP. We want to take this framework, where three companies offer and fulfill an all-inclusive job proposal together, and make it into the first case study for the entire group. That is our genuine ambition.
idealump’s President Miyahara comments, “I have high expectations for a structure where joint proposals—multiplying the strengths of our three companies—operate as a designed mechanism, rather than just by coincidence. As the leader in UI/UX and DX implementation, idealump aims to drive the creation of cross-group success stories.” I also believe intentionally operating as a system, rather than just by chance, will be the essential point of the coming year.
In my previous article about One Tech World, I said we chose to bundle together. I believe this past year was not a year of increasing the number of our arrows, but rather a year of bundling the arrows we had. The arrows didn’t break, but I honestly feel our bundling technique is still a bit loose. Within the D-POPS GROUP mission of “producing growth ventures that transform society,” One Tech World will play a vital role as a platform where these three companies can grow together while actively learning together and supporting each other. We won’t let the concept of a Venture Ecosystem remain only words; we will give it shape with actual projects and real work. I believe that is our role.
In the coming year, just how far can we aim with these bundled arrows? We will show the answer through the concrete results of our work.
That is all for now. I will share our results again next year.
techbeans inc.CEO Kazuhiro Maekawa