The big picture idea behind Macro is that non-technical employees should be able to build software to solve their problems. We are not the first to believe this. Many proponents of the no-code movement subscribe to a similar view.

But we want to shepherd non-engineers into a world where they are building software in a way that is very different from what other companies in the space are doing.

Consider Workflow Automation companies. These companies give users the ability to define automation recipes that orchestrate interactions among various cloud based services. With this kind of tool, you can define a trigger and a set of actions that should take place if the trigger is instigated, e.g. you can populate a Google Sheets spreadsheet with results once a form on Typeform has been submitted.

These tools are great for work that is simple enough that it can be automated according to predefined rules.

But not all work can be fully automated. Most work still—and we believe this will be the case for a long time—requires human involvement.

So what do companies do today for things that feel mechanical and repetitive, but which can’t be automated because they require human involvement?

They create checklists. And though most checklist-makers would never think of it this way, checklists are essentially a type of programming. This is an important insight and the core idea behind our company: we are going to turn today’s checklist makers into tomorrow’s enterprise app builders.

Come build with us.