Still not sure where your situation fits?
You do not need to diagnose the problem or choose the right technology before reaching out. Explain what is happening, what you want to improve, or what decision you are trying to make.
Clear expectations, practical choices, and direct communication from the first conversation through delivery and ongoing support.
Starting a project
We begin with the problem you are trying to solve. You do not need to know the correct technology, platform, or service name before reaching out.
InnoNate will ask enough questions to understand the goal, existing systems, important constraints, and whether the work fits a standard service or needs a custom scope.
Yes. Before approved work begins, you receive a written proposal describing the expected scope, schedule, InnoNate charges, and any third-party services expected to be required.
Third-party services are either paid directly through an account you control or clearly identified in the proposed arrangement. No new paid service is added without approval.
That is normal. Technical consultation can be used to compare options, understand an older system, choose a cloud or hosting service, estimate likely costs, or determine the safest next step.
A successful engagement may be a complete build, a repair, a written recommendation, or one focused hour that gives you a clear direction.
Ownership and handoff
You own your business content, branding, data, and the delivered project-specific work described in the proposal.
InnoNate retains ownership of reusable foundations, shared tooling, templates, and other pre-existing materials, while you receive the rights needed to use, operate, maintain, and modify the delivered solution.
Yes. You may request a complete, buildable, point-in-time copy of the delivered site or system at any time.
InnoNate will provide the handoff within a reasonable timeframe, together with the practical information needed to continue operating the delivered version.
Yes. You may move the delivered solution into accounts you control, choose another hosting provider, or hire another developer to maintain and extend it.
Customer-hosted projects have no required recurring InnoNate hosting fee. Ongoing support is available, but it is never required.
Good Bones is a reusable application foundation used in many InnoNate web projects. It is designed around portability, maintainability, clear ownership, and practical handoff.
You may use and modify the Good Bones code incorporated into your delivered project. Good Bones may not be extracted, repackaged, published, licensed, or sold as a standalone framework or unrelated customer product.
Hosting, domains, and support
The domain should be registered through an established registrar in an account you control. Registration and renewal fees are paid directly to that provider.
InnoNate can help you choose an available name, compare registrars, complete the purchase, configure DNS, and connect the domain to the finished site.
Basic Hosting & Maintenance includes managed hosting for one standard small-business website, SSL, deployment management, routine platform maintenance, and basic availability and usage oversight.
It does not include domain registration or renewal, content edits, new features, priority support, separately priced third-party services, or usage beyond the allowance identified in the proposal.
If unusual traffic, automated abuse, or technical activity creates a risk of excessive infrastructure charges, InnoNate will first attempt reasonable measures such as alerts, throttling, or limiting affected features.
A temporary restriction or pause may be used when necessary to prevent runaway costs or service harm. InnoNate will make reasonable efforts to contact you before disruptive action when circumstances allow.
Planned launches, announcements, and email campaigns may use a temporary Campaign Traffic Boost, with timing and expected usage agreed in advance.
Managed Care & Support provides priority email support, faster acknowledgment of requests, proactive follow-up, coordination of routine maintenance, and up to 30 minutes of minor assistance each month.
Included assistance does not roll over. Work exceeding the plan is estimated and approved before moving to hourly or project pricing.
Standard InnoNate support is not staffed as a 24/7 emergency service and does not include guaranteed around-the-clock response.
Customers with a genuine need for extended-hours or on-call coverage may request a separately designed support arrangement. Availability, escalation expectations, response targets, and pricing would be agreed in advance.
Requests under standard plans are acknowledged as promptly as reasonably possible, and the next appropriate step is scheduled based on urgency, availability, and the customer’s service arrangement.
Pricing, training, and future work
Prepaid blocks may be used across approved InnoNate projects or support requests for the same customer. Each new request is reviewed and scoped before work begins.
Purchased hours cover time worked and do not guarantee completion of a particular outcome within the remaining balance. Unless otherwise stated, blocks expire six months after purchase and unused time is nonrefundable.
InnoNate will notify you when the remaining balance may be insufficient and will not exceed the purchased hours without approval.
Yes. Larger projects or clearly defined outcomes may be quoted as a fixed-price engagement instead of hourly work.
The scope, price, expected result, and important assumptions are documented and approved before work begins. Changes outside that scope are discussed separately rather than added without approval.
Yes. Documentation, walkthroughs, administrator training, and practical handoff sessions may be included in the original proposal or added as separately scoped work.
InnoNate can continue managing the system, help your existing team take ownership, or support a gradual transition to internal operation.
InnoNate can help assess the systems, vendors, accounts, scripts, workflows, documentation, and support responsibilities your organization has accumulated.
That assessment can help determine what should remain outsourced, what should move inside the organization, and what technical roles or capabilities may be needed next.
Routine maintenance may include compatible platform improvements when they reasonably fit the customer’s service arrangement.
New modules, substantial upgrades, custom functionality, and future Good Bones features are not automatically included unless specifically covered by the proposal or approved as additional work.
You do not need to diagnose the problem or choose the right technology before reaching out. Explain what is happening, what you want to improve, or what decision you are trying to make.