Before starting out with my plans to turn metaexplorer into a business, I wrote a business plan – and because 2020 showed us what it thinks of plans – it will probably be obsolete soon. Nevertheless, the act of planning is important, not the plan itself.

And because I like graphs, illustrations and other visuals, here it is in the form of a business model canvas.

It’s a wild mixture of different ideas and directions I could see metaexplorer head to, the following months will show what’s going to happen.

Ideal scenario

In an ideal world, where all those ideas come true, freelance designer Joe could join company ÄCME, use his toolset of metaexplorer-UX-components to build a new portion of an application, without code. ÄCME’s design system would automatically be applied, which might uncover a bug in one of their UI components. UI-developer Jane fixes the bug, the change would be visible in the new portions as well as the old parts, and in other apps of ÄCME as well. Now Sandy is almost done with the server. In the team, they meet to discuss in front of a screen: The business logic looks like Excel with DMN/BPMN, a flow-diagram shows the data extraction with node-red, so Sandy and Jane can discuss how the Graphql Schema should evolve. With the new schema, Jane generates new non-visual components in Metaexplorer (one click) and drags them as input to Joe’s UX work. Because Joe uses dynamic place holders, metaexplorer automatically looks into ÄCME’s dictionary of visual components and decides for the best fit. The new part of the application looks and feels true to ÄCME’s design, but the new functionality helps ÄCME serve its customers even better.