About Crewkit
Crewkit is built by Martin Mooz, a designer and developer who builds tools that fit the way companies actually work.
Generic platforms make your team adapt to someone else’s idea of a workflow. Crewkit does the opposite: small, focused tools that follow your processes, your wording and your brand.
You talk to the person who builds your tools. No account managers, no hand‑offs, no feature bloat.
Frequently asked questions
How much does Crewkit cost?
Builds start from €1,500 for a first set of tools. The final price depends on which tools you need, how many locations and languages they cover and which systems they connect to. The first call is free and you get a clear quote. Request a quote.
How long does a build take?
A first set of tools usually goes live in four weeks: week 1 mapping your tasks, weeks 2–3 building, week 4 launch. Smaller builds can be faster, and new tools can be added at any time.
Can we add tools later?
Yes. New tools are added to the same instance whenever you need them. No migration, same address, no separate project.
Do we need a designer or developer on our team?
No. Every tool is made for the people who use it every day: front desk, office managers, marketing. If they can fill in a form, they can use Crewkit.
Where does our data live?
Every client gets a dedicated instance with its own deployment, database and address. Nothing is shared between clients. Tell us about your security and hosting requirements during scoping and we will plan around them.
Which tools does Crewkit connect to?
Today, Crewkit output goes straight into Outlook, Gmail, OfficeRND and print shops, sales pages send leads to HubSpot, and events are imported from the client’s website. SharePoint, Google Workspace, Slack or Teams and anything else with an API are connected on request.
Does it work in more than one language?
Yes. Tools can produce output in two languages side by side, with translation built in. At Scott.Weber, client-facing tools such as flyers, signs, client emails and meeting-room screens work in Czech and English.
What tech stack does Crewkit use?
Widely used, modern tools: React, TypeScript and Tailwind CSS, serverless functions and a Postgres database, hosted on Vercel. Nothing niche and nothing that locks you in.
Can we see it working?
Yes. Book a walkthrough and we show you the tools running at Scott.Weber Workspace: the real thing, not slides. Or try the preview on this site first.
We don’t know which tools we need. Is that a problem?
No, that is what the first week is for. We look at your workflows together, find the repetitive tasks and suggest the right tools. You don’t need a spec, just a clear picture of what slows your team down.
What about maintenance?
We take care of support and updates. If something needs to change, we change it. The terms are part of your quote.
Who owns the code and our data? Can we leave?
The code is ours and licensed to you. Your data is always yours. You can leave at any time and we hand over all your data. No vendor lock-in.
Licensing
Each Crewkit instance is built for one client. There is no shared platform and no one‑size‑fits‑all plan.
You get your own toolkit: your address, your brand, your tools. The licence covers the build and deployment of your instance; support terms are part of your quote.
First tools from €1,500.
Every build is scoped to your team: which tools, how many locations, which languages. Tell us what slows you down and you get a clear quote.