Clear answers for both sides of the workflow.

MediaSpoon is a contributor workflow and relationship management platform for publications, journals, newsletters, podcasts, research organizations, and content teams. It keeps the work from initial request through submission, review, approval, and publication in one place.

Contributor work is often scattered across email, direct messages, spreadsheets, shared documents, and calendars. MediaSpoon makes it clear who was invited, what is due, which version is current, what still needs approval, and what was ultimately published.

No. MediaSpoon manages the contributor workflow before and around publication. Approved work can continue into WordPress, Ghost, Webflow, Google Docs, Notion, or a custom CMS.

Not primarily. Publications start with contributors they already know and trust. Optional discovery is available only when the existing network does not cover a need.

A CRM records contacts and conversations. MediaSpoon connects each relationship to the actual contribution work: requests, deadlines, drafts, reviews, approvals, published results, and the history needed for the next collaboration.

A form captures an incoming response. MediaSpoon carries both sides through the complete relationship, including invitations, revisions, approval, publication history, and future requests.

Yes. Add past authors, trusted sources, researchers, advisers, podcast guests, and industry contacts, then begin sending structured requests immediately.

MediaSpoon is designed to support imports from spreadsheets and contact lists, with organization by expertise, role, topic, relationship, and preferred format.

Short expert commentary, news reactions, contributed articles, interviews, podcasts, video responses, research contributions, case studies, recurring columns, panels, and events.

Yes. Editors, researchers, writers, producers, and contributor managers can work in the same publication workspace, with requests, notes, submissions, and decisions kept together.

Yes. Selected wording, attribution, biography, title, and disclosures can be sent back for confirmation, creating a clear record of what was approved.

No. It complements your publishing stack. MediaSpoon manages contributor operations while your existing CMS remains the place where approved content is published.

Yes. Publication teams can keep internal observations, relationship context, format preferences, and follow-up reminders that contributors cannot see.

No. Your MediaSpoon account belongs to you and can support separate private relationships with multiple publications.

Yes. One dashboard can organize requests by publication, deadline, topic, contribution type, and status.

No. A publication sees only the requests, drafts, messages, and history connected to its own relationship with you.

Yes. A shared core profile can support publication-specific biographies, professional titles, disclosure statements, and preferences.

No. You can accept, decline, ask a question, request more time, or recommend another contributor without ending the publication relationship.

When approval is requested, you can review the selected wording, attribution, biography, title, and disclosures before confirming or requesting a correction.

Yes. Contribution history is private by default; you choose whether selected work appears in a professional portfolio.

The intended model keeps the core contributor experience free for legitimate publication relationships. Publications pay for workflow, team, and network management tools.

No. A publication can use MediaSpoon entirely with its own contributor network.

Yes. Contributors can opt out, choose topics and formats, limit visibility to paid work or approved publications, and mark themselves temporarily unavailable.

MediaSpoon is not designed as an open pitching directory. Discovery is intentional, permission-based, and focused on relevant invitations.

The model prioritizes relevance, contributor controls, publication approval, and trusted relationships over follower counts, request blasting, or the volume of profiles.

The contributor controls their reusable identity. Each publication separately controls its private notes and relationship-specific history.

The contributor keeps their account and reusable profile. Each side retains the records it is entitled to keep, subject to export, deletion, and retention rules.

The publication's relationship history remains in its workspace so useful knowledge does not disappear with an individual inbox.

They are designed as separate workspaces with relationship-specific access and private editorial notes.

AI may assist with tasks such as organization, transcription, summaries, and repetitive administration. Any use should remain visible and policy-controlled.

The product direction supports clear expectations around how submissions may be processed and when contributor consent or disclosure is required.

No. Technology can reduce repetitive work, but editors and contributors remain responsible for judgment, context, accuracy, and approval.

MediaSpoon is available by request for publications and contributors. Use the Request Access page to tell us how you plan to use the platform.

Publication plans scale by team size, contributor network, workspace needs, and advanced workflow features.

A small contributor list and one recurring workflow are enough. Start with the process you currently manage through email and spreadsheets.

Choose publication or contributor on the Request Access page and tell us how you work today. We will use that context to recommend the right next step.