Resources: useful content that we publish on Paralect pages
ℹ️
This page explains the type of useful content that we publish on Paralect website, target audiences and criteria that we apply to such resources. It’ll be useful for the Paralect team to explain specific areas of content that they can contribute to along with some guidance.
Resource is a piece of content useful for clients (or team) to solve specific startup problem, helping them build and grow their startups.
2 resource audiences:
- Clients (potential and current): startups, enterprises (specifically C-level / management)
- Team (candidates and current): product managers, marketing, design, developers, qa
Resource rules:
- A resource is something that people rather search in the internet or ask frequently on the private calls (sales or project calls)
- We should refer to resources often and use them ourselves . If we refer to a resource and open it often, it shows that it is useful for other people too. If we never refer and open resource, it’s most likely useless and should be avoided
- Strive to link resource to other pages and resources
- Resources need a hero image (used for OpenGraph too); most articles need some inner graphics too to make them engaging
- Each client resource should be published and distributed to social media
| Space | Target Audience | What is it / examples |
|---|---|---|
| Blog Articles | clients | - SEO-optimised articles that help build startups (things that people search in the google / ai chats) - Professional articles on product management, design, engineering, qa - Leadership thoughts on how the market evolves and how Paralect adapts - “Build in public” articles showing how we build specific products and lessons from it Examples: - 9 tips to build the right MVP today - Machine learning applied: image detection - Cognitive biases that drives customers decisions - Scoping the product: how to estimate an MVP easily (and accurately) |
| Help Articles / FAQs | clients | Knowledge base to explain clients how Paralect team works. Processes from presales to project end. Should answer potential intro-calls questions and project questions. It’s like big Paralect FAQ. Examples: - How project estimation works - First weeks / onboarding - How iterations are planned and released - What reporting is available to clients - How to give feedback to improve process - The tools Paralect uses for projects - Billing cycle / how you invoiced |
| Handbook Guides & Templates | team | “How to” articles describing how to build and manage startups. Only rules that we follow in Paralect and use ourselves internally (aka SOP — standard operating procedure) - How to estimate project MVP - How to organise meetings to make them productive - How to write compelling marketing articles Templates to solve common project tasks: - Project Estimation Template in Airtable - Project Start Checklist - Proposal Notion template |
| AI Tools | clients+team | Programmatic tools that help clients to build their startups - Landing page copy generator - Analyse startup competitors (features and pricing) - User persona generator - Tech roadmap generator |
| Directories | clients+team | The collections of helpful pages, optimised for programmatic SEO Examples: - No-Code Stack: modern tools to build startups (134 pages, 9 categories) - Kickstart: get $220k in tech discounts (16 pages) - Tech Stack: tech tools to build startups - Top free product management resources - Top-notch websites for design inspiration |
| Portfolio | clients | Paralect case studies and testimonials. Show clients what problems we solve in Paralect, build trust and confidence in our delivery skills. |
| Changelog | clients+team | Automatic updates for all resources published on the website. Handwritten updates with summary of what was released across Paralect. Examples: - New article: 2026 tech trends - New tool: Landing page generator - New help guide: How billing works - New case study: Clipwing |
Related resources
- How to write appealing marketing posts
