After launch

Post-launch support for websites, apps, and software

Once your system is in use, we help review early issues, fix bugs within the agreed scope, and guide your team through essential workflows.

Discuss support See the scope

The support period and scope follow your project agreement. New features and formal SLAs are discussed separately.

Support scope

Separate early fixes from new work

For a launched project, start with problems in agreed functionality. Plan new requirements as a separate phase.

Topics for early support

Review of core workflows
Check the paths your team or customers use after the system goes live.
Bug fixes within agreed scope
Report behavior that does not match the documented project scope.
Early usage guidance
Clarify access, user roles, and basic steps as your team adopts the new system.

Requires a separate agreement

New features, modules, or integrations outside the project scope.
Major redesigns or changes to business processes not previously agreed.
Formal SLAs, 24/7 coverage, or ongoing maintenance without a separate agreement.

By project type

What needs support?

The relevant workflows differ across websites, mobile apps, and operational software. Explore the matching service to understand its development scope.

Release support scopeHow we discuss bug reports, stabilization, and follow-up work after launch.WebsitesForms, admin access, and important page behavior after launch.Mobile appsLogin, notifications, and user flows as the app enters regular use.Operational softwareUser roles, data flows, and processes moving into the new system.

Support FAQ

Questions after launch

Do all projects automatically require monthly maintenance?

No. Many projects are healthy with initial stabilization, then next development phases happen only when clear, recurring needs arise.

What's the difference between bug fixes and new feature requests?

Bug fixes mean functionality within agreed scope isn't working as expected. New features mean new workflows, screens, reports, or requirements never in the original scope.

If the team still needs adaptation after launch, what should we do?

Clarify core workflows first, ensure access and roles are understood, then gather further changes as the next phase rather than mixing everything at once.

Is this initial support the same as formal SLA?

No. Formal SLA, on-call hours, or maintenance packages need to be discussed separately based on your project's operational rhythm.

Next step

Tell us what changed after launch

Share the affected page or workflow, when the issue occurs, and the result you expected. We can help distinguish bugs from new requirements.