Applied to the Yokatoko Business Plan Contest — A 4-Week Preparation Log

MAPRISE submitted an application to the Yokatoko Business Plan Contest's first-round screening, deadline May 12, 2026.

This post is a candid log of what we built in the four weeks leading up to the deadline, and how we used the contest as a forcing function. Hopefully useful for others considering applying or curious about launching a regional startup.

Note: the specific contents, numerical targets, and detailed revenue model in the submitted plan are kept internal for competitive reasons. This post focuses on the preparation process and using a contest as a forcing function.

What Yokatoko is

The Yokatoko Business Plan Contest is a regional bizcon co-run by Fukuoka Prefecture, regional SME support councils, and local financial institutions (Japan Finance Corporation, Fukuoka Bank, Nishi-Nippon City Bank, among others). It targets founders and "second-time founders" based in Kyushu / Fukuoka, with a two-stage format: document screening followed by a final pitch. The judges' table is expected to include regional banks, venture capitalists, local government, and established companies (including family businesses and listed firms), though the exact lineup varies by year.

Unlike Tokyo-centric bizcons, "contribution to the regional economy" is an explicit evaluation axis. The "earn in Tokyo, headquarter in Tokyo" story is less compelling here than "how will you change Kyushu's local industries?" and "what jobs will you create locally?"

MAPRISE is a GIS SaaS specialized for the Kyushu real estate / finance / homebuilder industries, so the regional contribution story aligns naturally with the evaluation axis. Not applying wasn't really an option.

Application structure (overview)

The 10-page business plan + supplementary materials followed a structure common to bizcon applications:

1. Problem definition (the pain the target industry faces)
2. Solution overview (what MAPRISE delivers)
3. How we read the market
4. Differentiation against competitors
5. Revenue model approach
6. Recent traction
7. Funding direction
8. Team composition and future structure

The concrete numbers and strategy details under each section relate to business competitive value and are omitted from this post.

What we built in the four weeks before the deadline

Backed out from the deadline, here's the "minimum viable demo state" we built starting mid-April:

Highlights:

• Data catalog covering all of Kyushu
• AI-integrated workflow: natural language → structured retrieval → graphs → PDF
• Bilingual landing (ja / en) + blog + RSS

Using the contest as a forcing function

Honestly, the real value of applying to a contest isn't winning — it's the forcing function of writing your business shape down to a deadline.

In the side-project phase, "I can start anytime" easily turns into "I never start." A contest deadline is an externally imposed end-date, and pushing toward it:

• Writing a business plan → forces clarity on target customer / solution / revenue model that was previously vague
• Needing to show traction → motivates polishing half-finished features into shippable state
• Being evaluated by third-party judges → focuses on market-valuable features, not self-satisfying features

Pass or fail, "the experience of being forced to articulate the shape of your business" is an irreversible asset for a founder.

What's the result

The first-round screening result isn't out as of publication (5/24). I'll report back here once results are announced. If we make it to the final pitch, I'll write a post-presentation retrospective too.

Pass or fail, the act of applying gets recorded as a milestone in MAPRISE's founding period.

Honest advice for future applicants

• Budget at least 4 weeks of prep: Writing a 10-page plan is qualitatively different from "trying to write something." Plan for full effort across four weekends
• Make traction visible: Combine production URL + demo video + screenshots + numbers. Judges see through prototypes that don't actually work
• Always build a competitive comparison table: Uniqueness only comes through in relative terms
• Tell the regional contribution as a story: Not just numbers — concrete pain points from named industry people (people-with-faces stories)

Next event

Pending the screening result, MAPRISE will continue feature polish toward the final pitch (date TBD).

In parallel, also published today (5/24) is a release post on the phased migration toward a next-generation architecture. Engineering-flavored — see that one if you're interested.

Questions, feedback, or contest experiences to share: info@maprise.jp.