Issue 01
It is unclear what maintenance includes
The boundaries among copy changes, configuration changes, defects, and added features are unclear, stopping decisions with every request.
Operations / Maintenance and Improvement
Define operational boundaries for confident post-launch decisions.
We begin by defining what to monitor, who makes decisions, and where additional development begins, creating a sustainable process for routine changes and incident response.
Starting point / 01
Before signing a maintenance contract, we put the service boundaries into words.
The word maintenance can easily blur minor fixes, incident response, feature additions, and external-service issues. We define the targets, request process, review environment, communication method, and conditions requiring an additional estimate so the operations and development teams can make consistent decisions.
Issue 02
Incident checks are scattered across services
Responsibilities for hosting, DNS, external APIs, databases, forms, and other components are not organized.
Issue 03
Small improvements remain unresolved
Even when daily observations are recorded, there is no process for prioritizing them or deciding when to act.
Prices are tax-inclusive estimates. External service fees, license fees, server costs, and changes after formal requirements are confirmed separately.
Scope / 02
Scope agreed before operations begin
The contract and estimate include only the items needed for the target system's importance and operating structure.
01
Requirements and handover review
We review the architecture, accounts, contracted external services, update procedures, and known issues to clarify the operational target.
- Inventory of the architecture and responsible owners
- Review of permissions, secrets, and update procedures
- Documentation of included and excluded support
Requirements and Technical Consultation Custom estimate
02
Minor fixes and routine changes
We apply agreed-scope changes to copy, images, settings, dependencies, and similar areas through a review environment and review process.
- Request intake and prioritization
- Advance review in Preview
- Review of change history and publishing results
Maintenance and Improvement From ¥30,000/month
03
Monitoring and backups
We define what should be monitored for downtime or anomalies and what data is needed for recovery, then establish monitoring and backups that fit the existing environment.
- Targets for uptime, error, and usage checks
- Backup targets and retention periods
- Notification recipients and initial-check procedures
Maintenance and Improvement From ¥30,000/month
Monitoring targets and backup scope are reviewed individually.
04
Incident response and change management
We establish a flow that records the symptoms, impact, and recent changes and separates temporary mitigation from a permanent resolution.
- Contact point and required information
- Records of triage, recovery, and recurrence prevention
- Conditions for contacting an external provider
Maintenance and Improvement From ¥30,000/month
Response hours and target scope are reviewed individually.
05
Improvement backlog and additional development
We collect day-to-day requests in one list and decide the order of implementation based on impact, urgency, and cost.
- Recording and organizing improvement candidates
- Separating small fixes from additional development
- Regular priority reviews
Maintenance and Improvement From ¥30,000/month
Additional development is estimated separately.
Process / 03
Operations begin after the target and communication method are defined.
If availability or response-time guarantees are required, we review those conditions separately from standard maintenance.
Step 01
Inventory
We review the architecture, contracts, permissions, update procedures, and current issues.
Step 02
Scope agreement
We define what is included and excluded, the request and review methods, and conditions requiring an additional estimate.
Step 03
Start of operations
We retain a history of requests, changes, reviews, and releases and work through the agreed flow.
Step 04
Regular review
We review issues and improvement candidates and adjust the next priorities.
Technical notes / 04
We also publish implementation decisions that support operations.
Acecore Systems technical articles explain specific decisions about updates, delivery, safety, and inquiry journeys.
Note 01
Sveltia CMS Implementation Guide
An overview of the operational flow and permission design from editing through review, PR, and publication.
Note 02
Secure Static-Site Delivery with Cloudflare Pages
Covers operational decisions about delivery architecture, security headers, and caching.
Note 03
Architecture for Extending a Corporate Site with Astro + Cloudflare
An overview of how to separate the static publishing foundation, dynamic features, CMS, and review and publishing flows.