DCS AIReach
Early access Get early access →
DCS Reach · early access

Plan once.
Publish everywhere.

Draft with AI, get a second person's approval, and schedule every channel on one calendar. Reach publishes on time and keeps a record of what went out, where and when.

Get early access → See how a post travels
  • Two-person approvalno self-approving
  • CSV / XLSXbulk import
  • One calendarevery channel
One desk

Eleven screens. Every part of publishing.

Create, plan, approve, publish and measure: each screen of the Reach dashboard, and what it does for you.

reach · dashboardIllustration
01 · Create

AI Writer

Captions, threads and articles from a one-line brief, in the tone you pick.

Open →
BriefAnnounce our new launch calendar, founder voice
LinkedIn post
X thread
Hashnode teaser
02 · Create

Composer

Write once, then shape a separate version for each account and check it before it goes out.

Open →
LinkedInXMediumDev.to
✓Length fits✓Media attached✓Link preview✓Hashtags
Request approval
03 · Create

Bulk Import

Upload a CSV or XLSX of posts, map the columns, check every row, then commit.

Open →
Your columnReach fieldCheck
captionCaptionMatched
platformProviderMatched
date + timeScheduled atAsia/Kolkata
approver_roleApprovalRow 14: missing
04 · Create

Assets

One media library per brand: upload once, reuse anywhere, delete safely.

Open →
▶Reused▶
05 · Plan & approve

Calendar

Drafts, approvals and scheduled posts for every channel on one calendar.

Open →
MON09:00
TUE11:3008:30
WED10:00
THU10:0014:00
FRI16:30
SAT12:00
SUN18:00
06 · Plan & approve

Queue

What is about to go out, what is going out now, and how many tries each post has had.

Open →
Launch notes, week 3Sending now
Thread: what we shippedNext · 14:00Queued
How we plan a monthWaiting for approvalApproval
Notes from the buildAttempt 1 of 3Retry
07 · Plan & approve

Approvals

A second person signs off before anything is published. Nobody approves their own post.

Open →
AREditor asked for approval · version 3
LinkedIn · Thu 10:00Three things we learned running our launch calendar on one desk.
ApproveRequest changesReject
✕  The editor cannot approve their own request
08 · Plan & approve

Overview

Drafts, approvals, today’s schedule, failures and blockers on one screen.

Open →
Drafts0
Awaiting approval0
Scheduled today0
Failed0
✓No blockers · nothing failed
09 · Publish & measure

Accounts

Each connected account, what it is allowed to do, and when it needs reconnecting.

Open →
LinkedInCan publish · analytics waits on a platform permissionConnected
XNot connected yetComposer
YouTubeNot connected yetComposer
InstagramMeta adapter on the wayOn the way
10 · Publish & measure

Results

Every published post with its platform ID, its link and its latest numbers.

Open →
Launch notes, week 3Published · urn:li:share:…4821✓
Thread: what we shippedQueued · not published yet·
How we plan a month of postsApproved · Fri 10:00·
11 · Publish & measure

Analytics

How each post performed, which channel brings sign-ups, and what to post next.

Open →
MTWTFSS

Numbers come from each platform once it grants read access.

How a post travels

Seven steps. One person in the loop.

Every post follows the same path, and every step is recorded. Publishing before approval is refused by the server.

  1. Draft

    Write it, import it, or let AI Writer start it.

  2. Check

    Each platform version is validated.

  3. Approve

    A second person signs off.

  4. Schedule

    It takes its place on the calendar.

  5. Publish

    The scheduler sends it at its time.

  6. Confirm

    The platform’s ID and link are recorded.

  7. Learn

    Numbers flow back to plan the next one.

Two-person approval

Nobody approves their own post.

Editors ask; a different person decides. The server enforces it, and an approval is tied to the exact version that will go out.

  • ✓Approve, reject or request changes, each on record.
  • ✓Self-approval is refused by the server.
  • ✓Edit after approval and it needs approving again.
Approval requestIllustration
AREditor asked for approval · version 3
LinkedIn · Thu 10:00Three things we learned running our launch calendar on one desk. A short thread on drafting with AI and approving as a team.
ApproveRequest changesReject
✕  The editor cannot approve their own request
Calendar · this weekIllustration
MON09:00
TUE11:3008:30
WED10:00
THU10:0014:00
FRI16:30
SAT12:00
SUN18:00

Solid cards are approved and scheduled; dashed cards are drafts waiting for approval.

One calendar

Every channel, every week.

Drafts, approvals and scheduled posts for all your accounts in one view, read from the real state of each post.

  • ✓Plan weeks or months ahead.
  • ✓Campaigns with their channels and progress.
  • ✓Overdue and waiting items stand out.
Bulk import

A month of posts from one sheet.

Upload a CSV or XLSX. Reach suggests the column mapping, checks each row and explains what fails, then creates drafts when you commit.

  • ✓Caption, hashtags, first comment, media, alt text, UTM tags.
  • ✓Date, time and timezone per row.
  • ✓Malformed files are refused before anything is created.
Bulk import · map fieldsIllustration
Your columnReach fieldCheck
captionCaptionMatched
platformProviderMatched
date + timeScheduled atTimezone Asia/Kolkata
hashtagsHashtagsMatched
first_commentFirst commentMatched
approver_roleApprovalCheck row 14: role missing
✓41 rows ready · 1 to fix · nothing published until approved
Channels

Every channel, from one composer.

Write once and Reach shapes a version for each account. LinkedIn is connected and proven; the rest are in the Composer or on the way, and we label each one honestly.

Connected and proven · 1
LinkedIn
In the composer · 7
XYouTubeMediumDev.toHashnodeDiscordNewsletter
On the way · 4
InstagramFacebookTelegramGmail

Every channel and its status →

Reachone composer
LinkedInConnected
XIn the composer
YouTubeIn the composer
MediumIn the composer
Dev.toIn the composer
InstagramOn the way
HashnodeIn the composer
FacebookOn the way
DiscordIn the composer
TelegramOn the way
NewsletterIn the composer
GmailOn the way
Results · recentIllustration
Launch notes, week 3Published · urn:li:share:…4821✓
Thread: what we shippedQueued · attempt 0·
How we plan a month of postsApproved · Fri 10:00·
✓Only posts the platform confirmed are marked published
Proof of publishing

A record of what went out.

Results lists only what a platform confirmed, with its post ID and link. Queued is never shown as published.

  • ✓Platform post ID and URL for every result.
  • ✓A unique publish key, so nothing goes out twice.
  • ✓Who drafted, who approved, when it went out.
Honest status

What works today, and what is next.

Reach runs inside DCS Intel today and is becoming its own product.

Working todayProven on staging and inside Intel.

  • ✓Composer: draft, per-account versions, platform checks, request approval.
  • ✓Two-person approval, enforced by the server: no self-approval, final decisions.
  • ✓Media library: upload, fingerprint dedupe, expiring private previews, safe delete.
  • ✓Bulk import of CSV/XLSX with column mapping and row-by-row checks.
  • ✓Connected accounts with a live check of what each account may do.
  • ✓Calendar, queue, results and analytics screens that show real state, never invented numbers.
  • ✓Separate workspaces per organisation; cross-workspace reads and writes are refused.
  • ✓AI Writer and the content queue inside DCS Intel.

On the wayNext, in this order of priority.

  • →Reach on its own address, separate from DCS Intel.
  • →Live publishing switched on for customers (held during founder acceptance).
  • →More channels connected end to end: X, YouTube, Instagram and Facebook first.
  • →LinkedIn analytics, once the platform grants the read permission.
  • →One inbox for comments and replies, with AI sorting and drafted answers you approve.
  • →Evergreen recycling, RSS and website-to-social automation.
  • →Brand memory for voice and style, and best-time suggestions from your history.
  • →Signed R-Series receipts for publish and approval actions.
Who it is for

Built for the people who post.

Creators & writers

Cross-post articles and threads to Medium, Dev.to, Hashnode, X and a newsletter.

See how →

Brands & agencies

Many brands, kept apart, with client sign-off built in.

See how →

Founder-led teams

AI coworkers draft, the founder approves. How DCS runs its own channels.

See how →

Publishers & newsrooms

High-volume scheduling with a clear record of what went out.

See how →
Questions

Straight answers.

What is DCS Reach?

The publishing desk inside DCS Intel, now becoming its own product. It takes a post from draft to approval to schedule to published, across your channels, and keeps a record of what went out.

Can I sign up today?

Reach is in early access. Today it runs inside DCS Intel for DCS AI’s own channels and invited teams. Ask for access and we will email you when your workspace is ready.

Which platforms does it publish to?

LinkedIn is connected and proven on staging. X, YouTube, Medium, Dev.to, Hashnode, Discord and newsletters are in the Composer; Instagram and Facebook come next. The Channels page shows the status of each.

Can AI post on its own?

No. AI drafts and proposes. A person approves, and the person who asked cannot approve their own post.

How much does it cost?

Pricing is announced at launch. Early-access teams hear first.

Is Reach part of DCS Intel?

Today, yes: it is the Reach (social) module of Intel. It is being separated into its own product with its own address; Intel users keep it.

Early access

Your channels, on one calendar.

AI drafts. A person approves. Reach publishes on time and keeps the record.

Get early access →Enterprise and publishers