Enterprise
The Asset Store package is everything most teams need. This page is for the cases where it isn’t — usually because your studio needs guarantees, integration help, or roadmap influence that a $50 asset can’t carry on its own.
If any of the below applies, get in touch: salepaun@autolayoutpro.com. One email, no form. Tell me what you’re building, the scale you’re operating at, and what’s on the line.
What an enterprise arrangement can cover
Each engagement is bespoke — the list below is a menu, not a package. Pick the parts that fit.
- Source-code licensing — full source access under negotiated terms, useful if your studio policy or platform requires you to vendor third-party code rather than depend on the Asset Store package.
- Priority support / SLA — a guaranteed response window for production issues, direct Slack / Discord / email access, and a named contact for your team’s leads.
- Sponsored feature work — pay to move something up the roadmap, or to build a feature that wouldn’t otherwise ship (custom layouts, importer for your in-house design system, platform-specific adapter).
- Custom integration — porting an existing UI codebase to AutoLayout PRO, building a thin in-house wrapper that matches your team’s conventions, or pair-programming with your gameplay / tools engineers during adoption.
- Training & onboarding — a workshop for your UI team covering the layout model, profiling, and the patterns that hold up at scale.
- Roadmap influence — formal input on what ships next. Sponsored teams’ use cases get weighted explicitly when I plan releases.
What this isn’t
- Not a different SKU. The Asset Store package and the source code are the same engine. Enterprise terms cover the services and licensing around it, not a secret “pro” build.
- Not a workaround for the Asset Store. If you just want to buy a seat or two, buy it on the Asset Store — that’s the right channel and it’ll always be the cheapest path. Enterprise terms exist for cases where a per-seat purchase legitimately doesn’t cover what you need (source access, SLAs, custom work).
- Not gatekeeping. Everything documented on this site is in the Asset Store build. The enterprise channel doesn’t unlock features — it unlocks services.
How it usually goes
- You email me with a short description of your use case, team size, and what guarantees / artifacts you need.
- 30-minute call so I can understand the context and you can sanity-check whether I’m a fit. No NDA needed for the first call; happy to sign one if you’d prefer.
- Proposal — scope, deliverables, timeline, price. Usually fixed-scope rather than time-and-materials, because that’s easier for procurement.
- Contract + kickoff. Most engagements run 2–8 weeks. Source licensing is a one-time arrangement; SLAs and sponsored development are recurring.
I’m one developer, so I take on a small number of engagements at a time. If timing matters for your project, email early.
Other ways to get attention without a contract
If your team isn’t at the point where a paid engagement makes sense, the Tell me what to build next section of the roadmap is the right channel. Real use cases — especially ones backed by a description of what’s blocking you in production — already move the priority list. You don’t need to pay to be heard.