For the projects the guild accepts, we waive the separate upfront development fee. We build something real first, so there is a working prototype to review before either side commits.
Every project is handled A to Z. DevOps, deployment, and infrastructure are part of the work, not a separate line item.
If we continue, you pay for the ongoing hosting and technical care that keeps the project running, maintained, and supported.
Selective · Prototype-First · No Lock-InWe do not accept every project. Some businesses apply directly; the Guild Master also reaches out personally through LinkedIn or email. An invitation starts a conversation, but it does not guarantee acceptance, and neither does applying.
The goal is to work where the guild can genuinely help, and where the relationship makes sense for both sides.
The prototype comes early and deliberately, because reacting to something real beats defining everything in the abstract.
A short exchange is usually enough: LinkedIn or email, your existing site, and whatever you care to share. We do not require a long discovery process first.
For accepted projects we build the first prototype at no cost. It gives both sides something real to react to.
We review the prototype together: what works, what needs to change, the functionality and integrations required, and the actual size of the project.
If the direction turns out to be materially off, we may build a second prototype. Otherwise we continue from the first.
With the scope clear, both sides decide whether to continue and we confirm the exact recurring price. There is no obligation to proceed simply because a prototype exists.
We complete the agreed scope, normally with up to 2 structured revision rounds before launch. After that the project continues under ongoing hosting and technical care.
Two parts, and only one of them is a bill.
Accepted projects pay no separate fee for the initial build, across every kind of work the guild takes on.
A recurring service fee that keeps the project running, maintained, and supported after launch.
The price depends on the scope, complexity, and support the project actually needs, and it is confirmed after the prototype review, never before.
The goal is for clients to stay because the service is useful, not because leaving is technically impossible.
Where reasonably possible you can inspect the code and project materials. You may stop the service and migrate the project yourself, or hire another provider to do it.
Sensitive production systems may use read-only access rather than full administrative access. One incorrect production change can break the application or expose data, so that restriction is about safety, not lock-in.
No. For accepted projects there is no separate upfront development fee, but ongoing hosting and technical care is a paid service.
No. Projects are accepted selectively. Applying, or receiving a direct LinkedIn or email invitation, does not guarantee acceptance.
No. The first prototype is a required part of the process for accepted projects. A second prototype is optional, and only used when the direction changes significantly.
After the first prototype is reviewed and we discuss the real project scope. It is never quoted before there is something real to look at.
Yes. The guild does not support vendor lock-in. You may move the project yourself or hire another provider to migrate it.
Tell us briefly about your business and what you would like to build. If it looks like a good fit, the next step is the first prototype.
Applying does not guarantee acceptance. Projects are taken on selectively.