Frequently Asked Questions

Clear answers about the work, the process, and whether Gilded Goose is the right operating partner for your practice. If your question is not covered here, send a note through Contact.

Ask a Question

  • Gilded Goose lowers the risk by establishing a clear baseline first, defining what success means for your practice, and tying every recommendation to measurable operating signals. You will always know what changed, why it changed, and whether the numbers support the next investment.

  • Usually not. Work begins with how the current stack actually behaves, what the team can sustain, and where data or ownership breaks down. Some tools stay, some are simplified, and new technology is added only when it earns its place.

  • Yes, payment plans are available on some fixed-scope projects, because a strong operating system should not have to wait for perfect cash flow. Payment can be divided across an initial deposit and project milestones, and an approved portion may be deferred under written terms with an agreed premium and a set due date. Ongoing retainers are billed in advance and are not deferred. Plans often make the most sense for practices where cash depends on incoming leads and a faster pipeline has a clear near-term return—law firms, private-practice medicine, accounting, advisory, and similar founder-led services.

Tools & Services

  • Tools are chosen for how well they fit your goals, your team's capacity to actually use them, your data requirements, and the cost of added complexity. There has not yet been a platform that could not be learned and put to work, which means the recommendation is never limited by what is familiar, only by what serves you. The aim is always a reliable stack the practice can run itself, not the largest possible architecture or a template borrowed from a very different business.

  • No, Gilded Goose does not sell or resell software, and that independence is the point. Advice stays free of vendor kickbacks, and every license and media dollar stays with the client. The only incentive is a stack that works for you, which is exactly why the recommendations can be trusted.

  • Yes on both counts. Systems such as HubSpot, Salesforce, or MyCase stay in play when they serve the practice, and replacement is recommended only when a tool genuinely cannot support the goals. Selecting and implementing new software that fits how the practice grows is just as much a part of the work as cleaning up what already exists. Fifteen years spent connecting stacks across finance, healthcare, high tech, agencies, and legal means the wiring between your tools gets the same attention as the tools themselves.

  • The access required depends on scope, and it often includes advertising accounts, CRM and marketing automation, analytics, the website or CMS, and call tracking. Requirements are confirmed before work begins so the audit reflects how the system truly operates rather than how it is assumed to work, because the honest picture is where the recoverable time and money are usually hiding.

Engagement & Process

  • Both, whichever moves the work forward faster. Gilded Goose is based in Colorado, with prior work spanning coast to coast and internationally, so distance has never been the constraint on a good result. Onsite time is used when standing in the room changes the outcome. Remote work is used when that is enough—and it often is—because fewer distractions mean faster progress, including off-hours work that keeps systems running without burning your team’s day.

  • Usually not. Work begins with how the current stack actually behaves, what the team can sustain, and where data or ownership breaks down. Some tools stay, some are simplified, and new technology is added only when it earns its place.

  • Scope and price are agreed before any work begins, so you are buying a defined outcome rather than open-ended hours. Defined projects are billed as fixed fees, and ongoing stewardship uses a retainer with clear boundaries. The budget information you share on the Contact form shapes a genuinely useful first response, so instead of a one-size-fits-all package you get a plan sized to the gaps that are actually costing you growth.

  • Yes, and enablement is treated as part of the deliverable, not an afterthought. When it is in scope, the work includes documentation, talk tracks, and operating rhythms the team can carry long after the build is complete. Implementation and enforcement still belong to the practice; as an outside partner there is no honest way to force adoption from the outside. What stays available is consistent reporting, clear readouts, and plan revisions when the numbers show the system drifting. The goal is a practice that can run without a permanent dependency on any consultant.