Marketing Agency Operations Automation Tool Development Example
* Actual cost, timeline, and scope vary by factors such as number of users, existing data conditions, and external system integrations.
This project originated when a small consulting firm realized that creating monthly reports for clients had become a significant burden for its staff. Previously, at the beginning of each month, the person in charge logged into multiple advertising platforms and analytics tools to download CSV data manually. They then used Excel macros to generate charts, converted them into client-specific PDF reports, and attached them to individual emails.
Once the firm surpassed 20 clients, this manual reporting process took more than three full days, cutting into their core consulting work. Furthermore, the risk of copy-paste errors and sending reports to the wrong addresses had become a pressing issue.
Proposal and Estimation Highlights
When consulted about operational efficiency, we proposed focusing on a "single-purpose tool that allows one staff member to complete the task with a single click once a month," rather than building a large-scale customer relationship management (CRM) system or a custom dashboard from scratch.
By intentionally omitting client-facing login screens, complex permission management, and database construction, we significantly reduced development hours. We adopted a stateless architecture that fetches data from external APIs, generates reports on the fly, and automates email delivery. This approach made it possible to deliver the project for ¥380,000 before tax over approximately 4 weeks.
To keep costs low, instead of perfectly replicating the existing Excel design, we replaced it with a simple HTML/CSS layout that could be printed from a web browser. Additionally, we used AI assistance to write test code for the API integrations, further improving development efficiency.
Deliverables and Feature Scope
The initial release was limited to a minimal administration screen for the internal reporting staff, external API integrations, and an email delivery function. The system was not designed to store past report histories; instead, sent reports were retained in the staff member's email outbox (via BCC).
Workflow and Screen Overview
| User | Main Actions | Practical Use Case |
|---|---|---|
| Reporting Staff | Select target month, execute data fetching, preview reports, and send in bulk | At the beginning of the month, the staff member opens the admin screen, selects "Previous Month," and clicks "Generate Reports." They briefly preview the generated reports for all clients and, if there are no issues, click "Send All." |
Main Data Managed by the System
| Category | Main Fields |
|---|---|
| Client & Configuration Info | Client name, destination email addresses, and integration account IDs (maintained as configuration files) |
| External Fetched Data | Monthly aggregated values such as impressions, clicks, conversions, and costs |
| Output Reports | Monthly summaries and trend charts for key metrics (HTML and PDF formats |
Technical Architecture and Security Policy
Because the system is used only by specific internal staff, we adopted a serverless architecture to minimize operational costs and maintenance efforts. Client configuration data and API keys are managed as secure environment variables and configuration files rather than in a database.
| Technical Area | Implementation Approach |
|---|---|
| Front End | A simple web interface designed for PC use by the staff member, built with a lightweight Vue.js-based framework. |
| Back End / API | Implemented as serverless functions in a Node.js environment. These handle external API requests, data aggregation, PDF generation, and email delivery. |
| Database | Not used. We adopted a stateless architecture to eliminate infrastructure costs. |
| Authentication and Authorization | Limited to Basic authentication or simple password authentication for the staff member, omitting complex user management features. |
| Quality Assurance | Conducted integration tests to prepare for external API changes and visual checks to prevent layout issues in the generated PDFs. |
Timeline and Delivery Process
Given the short four-week timeline, the first week was dedicated to reviewing the existing Excel report format and mapping it to the data fields available from the APIs.
| Phase | Timing | Work Completed and Client Participation |
|---|---|---|
| Step 1: Scope Refinement and Data Review | Week 1 | We reviewed the existing Excel reports and the API specifications of the target SaaS platforms. For custom metrics not available via API, we defined calculation logic. |
| Step 2: Prototype Implementation | Week 2 | We built a prototype that fetched data from the actual APIs and displayed it as a report in the browser. The client reviewed the chart visuals at this stage. |
| Step 3: Email and PDF Implementation | Week 3 | We integrated functions to convert the generated reports into PDFs and email them to configured addresses. |
| Step 4: User Acceptance in the Test Environment | Early Week 4 | The staff member tested the application to confirm usability and the content of the automated emails. |
| Step 5: Delivery, Go-Live, and Payment | Late Week 4 | The application was deployed to the production environment, and a basic configuration manual was provided. The full amount was invoiced after acceptance (typically within five business days of release). |
Payment Terms
As a general rule, no up-front payment was requested. There was no payment at contract signing; the full amount was invoiced only after all development work was complete and the client had completed acceptance.
Cost Breakdown
The following amount includes requirements alignment, external API integration, testing, and production release. It does not include database construction, client-specific login features, or complex permission management.
| Item | Cost Before Tax | Scope |
|---|---|---|
| Requirements Definition and Project Direction | ¥50,000 | Analyzing existing reports, reviewing API specs, and defining output fields |
| UI/UX Screen Design | ¥30,000 | Simple layout design for the staff admin screen (1–2 screens) |
| Front-End Development | ¥80,000 | Implementing the report preview screen and user interface |
| Back-End and API Integration | ¥160,000 | Fetching data from external SaaS, aggregation logic, PDF generation, and email delivery |
| Testing and Implementation Support | ¥60,000 | AAPI integration testing, production setup, and creating the configuration manual |
| Total | ¥380,000 | 税込 ¥418,000 |
Currency Options for Quotations and Invoicing
In addition to Japanese yen (JPY), quotations and invoices can be issued in U.S. dollars (USD) or other currencies upon request. The applicable exchange rate, conversion basis, and any bank or payment-provider fees will be confirmed in advance for each project.
Supplement: Estimated Third-Party Service and Maintenance Costs After Launch
Because this system uses a serverless environment and a stateless architecture with no database, running costs during operation are kept extremely low. The following are estimated monthly costs required after the production launch, separate from the initial development fee.
| Category | Estimated Monthly Cost Before Tax | Nature of Cost and Main Inclusions |
|---|---|---|
| Third-Party Cloud Service Charges (at cost) | ¥0〜¥3,000 | Usage fees for the serverless execution platform and email delivery service (e.g., SendGrid). Due to low execution volume, this often falls within free tiers or incurs only minor actual costs paid to cloud providers. |
| Minimum Maintenance and Operational Support | ¥10,000〜¥15,000 | Monitoring for external API specification changes, minor layout adjustments, and monthly functionality checks. Major overhauls or integrating new SaaS platforms require a separate estimate. |
| Estimated Monthly Total | ¥10,000〜¥18,000 | A low-cost operating assumption based on the items above. The amount varies with the number of reports sent and additional integrations. |
Staff Comment
When budget and time are limited, narrowing down "what exactly needs to be solved by the system" is the key to success. In this case, there was a clear pain point: "Manually creating different reports for each client every month is exhausting."
Therefore, we discarded the idea of building a fancy dashboard or a client portal, and strictly committed to a "tool that simply gathers data in the background, turns it into a PDF, and sends an email." As a result, a task that took the staff member several days at the beginning of the month was reduced to a few minutes of button clicks.
Typical Scope for Common Add-Ons
Once the operation is established, if a request arises to "allow clients to view their latest data at any time," developing a Client Dashboard (My Page) is a logical next step. Because this requires building a customer database and secure login features, such an addition typically costs ¥600,000–¥900,000 before tax and takes about 1.5–2 months.
Starting with small, reliable business automation frees up time for core consulting work. Expanding the system only when the need arises is a highly cost-effective investment approach for small businesses.
How It Started