Loading Goldspire…
Loading Goldspire…
Fixed price for agreed work; change orders when the shape moves. Weekly demos and staging you can use. The next section is the plain read before you sign; after that, definitions for how we use words on this site — then phases end to end.
Marketing pages sketch typical patterns. Your signed proposal is the checklist: if it is not listed, it is not included — we quote changes instead of quietly expanding scope.
In every signed engagement
Often depends on your accounts or add-ons
Payments in the product
When agreed: we wire the product to your payment provider (often Stripe); merchant approval and live charges stay with you.
App store listings
When mobile is agreed: we ship builds; public listing needs your developer accounts and store review time.
Project hub
When agreed: a private link for documents and status — separate from your customer-facing product.
Not included unless we sign it
Store review and account setup are predictable delays — we plan for them once we know who holds which login. They gate the public listing date; they do not block building the product in staging.
Expand store checklist
| Owner | Task |
|---|---|
| Client | Apple Developer Program enrolment (paid) & legal entity on record. |
| Client | Google Play Console account & merchant / tax profile if selling in-app. |
| Client | Privacy policy & support URL live (stores require URLs). |
| Shared | App Store Connect + Play Console access for Goldspire as agreed (min access to ship). |
| Studio | Builds, signing config, TestFlight / internal testing, submission drafts when mobile is in scope. |
| Studio | Respond to review questions with you in the loop — we do not control approval timelines. |
| Either | Screenshots, promo text, age rating questionnaire — we draft from the product; you approve copy. |
We split work into three layers so a fixed-price path still delivers a complete branded product — without hiding invention inside a “basic” price. Your proposal names surfaces, integrations, and delivery checkpoints; if it is not listed, it is not included.
Look and voice
How the product feels like yours: colour, typography where the template supports it, logo placement, and copy on the screens listed in your proposal.
Typical clone engagement: A full brand pass within the template’s existing layout patterns — not a blank canvas, but a credible branded product. Whole-app redesign, bespoke illustration systems, or new marketing sites beyond agreed surfaces are quoted separately or move to a higher tier.
Shape within the shipped product
Turning knobs the architecture already supports: categories, labels, onboarding steps, feature toggles, and copy tables — without changing the underlying mental model.
Typical clone engagement: Meaningful tailoring so the template matches your audience, still inside the same flows and data shape we shipped. New entities in the data model, new admin workflows, or “competitor parity” feature lists belong outside clone economics unless written in.
New product work
Anything that changes what the product *is*: new flows, new rules, new integrations, or new surfaces that were not part of the named template.
Typical clone engagement: Bugfixes, fit-and-finish, and small wording or ordering tweaks inside flows that already exist. Net-new invention upgrades to Tier 2 (new template on an existing blueprint) or Tier 3 (new blueprint), or a change order if you stay on clone.
Paid discovery is available when you are not sure which path fits — we scope honestly before engineering starts.
Every engagement follows the same spine: we agree scope in writing, you accept and pay milestones through a private project hub, we build in staging you can review, then we cut over production and transfer what you own.
Step 1 · Before contract
You
Send a brief or book discovery. We reply with fit, a suggested path (adapt a template, new template, or ground-up), and a price band.
Studio
We qualify the brief, pick the right starting economics, and draft proposal boundaries before any serious build.
Step 2 · Contract & kickoff
You
Sign the proposal. Receive a project hub link — accept terms, pay the first milestone, complete the kickoff checklist (and product intake when applicable).
Studio
We issue your hub link, track acceptance and payments, and provision your tenant on our stack.
Step 3 · Build
You
Weekly demos on staging. Async updates between demos. Change requests outside scope → written change order before more build.
Studio
We run identity and configuration phases, hit agreed checkpoints, and keep the runbook green until UAT.
Step 4 · Go-live & after
You
Production release per contract. Repos and runbooks transferred. Optional retainer agreed separately if you want ongoing care.
Studio
We complete handover, close the engagement in our systems, and archive the hub when done.
Plain definitions for precision. If anything here conflicts with your signed proposal, the proposal wins.
Discovery
Typically ~1 week
We clarify what you are building, for whom, and whether we are the right studio to deliver it.
Design & specification
Typically 1–2 weeks
We lock brand direction and technical shape before engineering — so build does not drift.
Build
Typically 4–18 weeks
Weekly demos, staging you can use, and clear async updates between demos.
Go-live & handover
Typically ~1 week
Production deployment of the release described in your proposal, plus handover of repos and runbooks as scoped. Not App Store approval, merchant onboarding, or unlimited post-release support unless written in.
Fixed boundaries, not open-ended drift.
We price agreed scope — template adaptation, new template, or new foundation — not vague hourly buckets. Meaningful shifts become written change orders before more engineering.
You own the IP.
Source code, schema, deploy configuration, and brand delivery — transferred on the schedule in your contract to your GitHub (or equivalent) and your cloud accounts.
One studio end to end.
The people who shape the system build and ship it. Fewer intermediaries — clearer accountability for the release named in scope.
We do not disappear at go-live.
Many teams want a scoped retainer after handover — hours, channel, response expectations — agreed in writing when you need it, not bundled silently into build.
Send the shape of what you are building. We will reply with fit, a suggested path, and a price band — straight, not scripted.