1SecondCopy / Business overview
2021–2026Documented operating span
Founder
An automated agency.
Built with
2021 AI.
An entirely automated content-writing agency, built with software and AI from 2021. The agency remained operational until 2026. Explore the operating systems behind its acquisition, production, delivery and finance.
Explore the nine systems
01 / Business context
A distributed team.
A repeatable service.
By 2021, 1SecondCopy was an entirely automated content-writing agency, according to co-founder Noah Edis. The business achieved this with the software and earlier-generation AI available at the time, years before today’s models.
At its peak, 1SecondCopy had 20 team members across Canada, the Philippines and Australia. The agency produced content for eToro, NordVPN, Wise and other established businesses.
The operating challenge extended through the whole service: identify a prospect, understand the client, prepare the right people, assign the work, review its quality, deliver it and reconcile the money around it. Each handoff needed to preserve enough information for the next person to act.
As a co-founder, Noah designed and implemented workflows, diagnosed integration problems and trained the team. Co-founders, collaborators, writers, editors and operations staff contributed to building and running the service.
02 / Inside the systems
The people.
The process.
The systems behind both.
Choose a system to follow its inputs, decisions and handoffs.
Select a system, then select any step for the detail.
- Client instructions and templates
Reusable client requirements and article-specific briefs stay attached to the production task. - Ready → Processing
Operations checks readiness; status changes start resource preparation and expose progress. - Create the article workspace
Find the client Projects folder, create an article folder and copy the writing template. - Shared article task
Persist the workspace link and use stage statuses and the execution link for troubleshooting. - Move before assigning
Native ClickUp automation moves the task so guest writers can be assigned in the destination. - Resolve parent and subtask owners
Read default owners; filter missing identifiers before setting actual assignees. - Article-level Harvest project
Use the client ID and article/task identity, then store the project ID on the task. - Reporting record
A Google Sheets row tracks the article as target and later final production facts develop. - Choose the production model
Client defaults support separate writing/editing owners or one full-stack producer. - Research and draft
A writer uses the brief, working document and sources; AI assistance still requires judgment. - Separate editorial review
An editor evaluates claims, originality, formatting and the client checklist. - Full-stack writing and editing
One assigned person performs both writing and editorial work for this production type. - Ready work and final facts
Final word count and logged time support submission preparation and reporting. - Update reusable editorial guidance
Generalize recurring client feedback into rules for related drafts and later assignments.
Explore the individual workstreams developed at different stages of the business.
03 / System directory
Choose the part
you want to understand.
Explore the systems behind the business, from the initial trigger to the team’s next action.
Growth
Database-driven lead generation & outreach
Search for buying signals across several platforms, combine duplicate leads, research their businesses and prioritize email or LinkedIn outreach.
Database, multi-platform scraping, enrichment, AI scoring and cross-channel outreachExplore the system System 02GrowthClient communications
Keep shared conversations useful: retain context, delegate replies, review drafts and turn accepted requests into production work.
Shared-inbox procedures and bounded integration testsExplore the systemPeople
Hiring & paid trials
Carry applicants from structured intake through two-stage human review to a record-linked paid writing trial.
Configured intake and human review; payment intake partialExplore the system System 04PeopleTeam onboarding & time tracking
Help new contractors confirm their working terms, gain access, learn the production process and record time correctly.
Operating procedures and test-account trainingExplore the systemDelivery
Client onboarding & project setup
Capture the client’s requirements once, prepare their workspace and carry the right instructions into each new article order.
Configured provisioning and documented manual checksExplore the system System 06DeliveryContent production & editorial quality
Give writers and editors clear ownership, reusable client context, quality gates and a route for feedback and questions.
Operating workflows, training and separate experimentsExplore the system System 07DeliveryDelivery & revision handling
Deliver reviewed articles through the right channel and reopen the original assignment when the client requests changes.
Delivery workflows and troubleshootingExplore the systemFinance
Client invoicing & cost reporting
Prepare reviewable bills from completed work and connect project activity with the source data needed to understand cost.
Draft invoice workflows; reporting under reconciliationExplore the system System 09FinanceContractor invoicing & payment preparation
Use recorded time and dated additional amounts to prepare invoices, collect signatures and draft payments for approval.
Documented preparation with human payment releaseExplore the system04 / Contribution & scope
Build the workflow.
Make it operable.
The agency’s operating systems connected sales, hiring, content production, delivery and finance. Reusable briefs and templates gave the team a consistent starting point, while linked records kept work moving between tools.
Noah combined hands-on integration work with day-to-day operating ownership. He maintained client references, investigated repeated delivery triggers, clarified invoice pricing and trained teammates to resolve failed handoffs.
Human review remained part of the workflow wherever quality or judgment mattered. Clear ownership, practical troubleshooting instructions and escalation paths helped the team operate and maintain the systems.
Explore other project work ↗