PHPTRAVELS Editorial
Write for us: travel technology, booking platforms and tourism SaaS
PHPTRAVELS Editorial publishes practical, verifiable articles from the people who build, run and market travel technology. This page is the commissioning brief: the topics we want, what a pitch must contain, the house style and how a draft moves from pitch to publication.
- 1,200 to 2,000 words
- Byline with author and company
- No paid placements
- Agencies may pitch for clients
The commissioning brief
Write for us if you build, run or market travel technology
The blog is read by agency owners choosing a booking platform, the IT leads who run one and the developers who connect it to suppliers. Every piece is judged on the same test: a clear problem, a replicable approach and real outcomes.
Published articles appear on the Blog next to our own writing about the Platform overview and its All integrations. We are a tourism SaaS company, so travel technology and booking-platform pieces are the closest fit and get the fastest, most specific feedback.
PHPTRAVELS Editorial is an industry publication, not a link marketplace. We do not sell guest posts or accept payment in exchange for a link, and outbound links may carry nofollow at the editor's discretion.
Who we publish
- SaaS founders and product leaders
- Travel-tech and integration engineers
- B2B SaaS marketers and growth operators
- Lifecycle, email and demand-gen specialists
- SEO and content leads in SaaS or travel
- RevOps and marketing-operations practitioners
- Data, analytics and experimentation leads
- Customer-success and retention strategists
- Platform and integrations product managers
- Publication
- PHPTRAVELS blog, English first
- Audience
- OTA and agency owners, travel IT leads, integration developers
- Formats
- Tutorial, case study, teardown, buying guide, benchmark
- Length
- 1,200 to 2,000 words; longer if every section earns it
- Byline
- Author name, role and company; bio link allowed
- Fee
- None paid, none charged
- Review
- Editor pass plus subject-matter check before publication
Topics board
Four lanes, one editorial standard
Pick the lane that matches your experience. Travel technology is our home turf, so those pitches get the quickest and most detailed notes; every lane goes through the same review.
Travel technology and booking platforms
9 topics
- 01GDS and airline NDC integrations: setup, caching and fallbacks
- 02Bed-bank mapping, pricing and availability for hotel APIs
- 03Search and pricing performance: latency, retries, timeouts
- 04Payments and checkout: 3-D Secure, refunds, chargebacks
- 05Multi-tenant white-label portals: roles, markups, contracts
- 06Travel CRM and lifecycle automation for agencies
- 07Reporting and reconciliation: markups, commissions, settlements
- 08AI and automation in booking, support and personalisation
- 09Booking-engine architecture, vendor selection and buying guides
Tourism SaaS
7 topics
- 01Platform strategy, architecture and multi-tenancy
- 02OTA and agency product design
- 03Pricing and monetisation models
- 04B2B travel SaaS sales and onboarding
- 05Customer success and retention in travel SaaS
- 06SaaS versus custom-built travel software
- 07Market trends and benchmarks
SaaS and B2B SaaS
6 topics
- 01Content marketing and SaaS SEO
- 02Demand generation, PPC and paid acquisition
- 03Email marketing and lifecycle
- 04Product-led growth and pricing
- 05Product strategy and product-market fit
- 06Case studies, white papers and tool reviews
Business software
6 topics
- 01ERP and accounting software
- 02HR tech and payroll
- 03CRM and help-desk software
- 04Project management and productivity tools
- 05POS systems
- 06Cloud platforms
A topic not on the board is still worth a pitch if it meets the standard above. A topic on the board is not a guarantee of acceptance.
Anatomy of a pitch
What an accepted pitch looks like
Two pitches for the same subject, side by side. The difference is not the topic but the specificity: a named problem, a stack, a method the reader can repeat and an outcome that can be checked.
- Working title
- Reducing API latency for multi-supplier hotel search
- Audience
- Developers and IT leads running an OTA with two or more bed-bank APIs
- Problem we solve
- Search pages waited for the slowest supplier; abandonment rose on mobile
- Outline
- 1The starting setup: three suppliers, sequential calls
- 2Per-supplier timeouts and a partial-results response
- 3Caching static content versus live availability
- 4What the dashboards showed before and after
- 5The checklist we now apply to every new supplier
- Assets
- Timing charts, redacted config, the checklist as a table
- Bio
- Lead engineer at an OTA; writing on behalf of the company
Specific stack, a replicable method and outcomes the reader can verify. The editor asks for the before-and-after numbers and the config excerpt.
- Working title
- Top 10 ways travel businesses can boost performance
- Audience
- Travel businesses
- Problem we solve
- Many companies struggle with performance
- Outline
- 1Introduction
- 2Why performance matters
- 3Ten tips
- 4Conclusion
- 5About our tool
- Assets
- Stock images
- Bio
- Content writer; the client wants a do-follow link to its pricing page
No named problem, no stack, nothing a reader could repeat, and the link is the goal rather than the article. The editor replies with this brief.
What the editor looks for
- 01A clear problem in a named context: OTA, agency, portal or supplier
- 02A replicable approach with concrete steps
- 03Outcomes the reader can check: timings, rates, revenue, time saved
- 04Screenshots, configs, queries or templates the reader can reuse
- 05Benchmarks for latency, caching or error handling where relevant
- 06A neutral, practical tone with claims backed by evidence
House style
Style rules for guest posts
Six rules that decide most edits. Follow them in the draft and the review is about substance, not rewrites.
| Rule | Instead of | Write |
|---|---|---|
| 1Claims need evidence | Instead ofOur caching layer makes search dramatically faster. | WriteAfter per-supplier timeouts, the search page rendered partial results within 2 seconds instead of waiting up to 9. |
| 2Headings say what the section does | Instead ofThe ultimate guide to travel APIs | WriteCaching static hotel content while keeping availability live |
| 3Links support the point | Instead ofThree links to the sponsor's pricing page | WriteOne product mention in the bio; in-body links only to sources the reader needs |
| 4Neutral, first-hand voice | Instead ofLeading travel businesses everywhere are leveraging AI. | WriteWe added an AI reply draft to the support inbox; agents still send every message. |
| 5Original and unpublished | Instead ofA rewrite of a post already on the client's blog | WriteNew work, written for this audience, with the brand relationship disclosed in the pitch |
| 6Visuals you have the right to use | Instead ofStock photos of airports | WriteYour own screenshots, charts and tables, with sensitive values redacted |
Submission process
From pitch to published
Six stages, each owned by one side. You always know what the next step is and who holds it.
- 01You
Pitch
Send the working title, audience, problem, outline, assets and bio by email.
- 02Editorial
Editor reply
An editor accepts, declines or asks for a sharper angle.
- 03You
Draft
Write the piece to the brief, 1,200 to 2,000 words, with your own visuals.
- 04Editorial
Review
An editor pass for clarity and structure, then a subject-matter check for accuracy.
- 05You
Revisions
You may receive notes before final acceptance; one round is typical.
- 06Editorial
Published
The article goes live on the blog with your byline, role and company.
Editorial standards
Original and practical
Unpublished work with actionable detail and real-world implementation.
Clarity and voice
Plain language, a human tone and claims backed by data or working examples.
Accuracy review
Editor and subject-matter validation for correctness, structure and completeness.
Bylines and attribution
Credit with author name, role and company; visuals under clear usage rights.
No paid placements
Acceptance is based on editorial merit only. No fees in either direction.
Send your pitch
Email the editorial desk
Pitches go to the editorial inbox. Copy the template, fill it in and send it; a general question about contributing can also go through the contact page.
Marketing and SEO agencies
You may pitch on behalf of a travel-tech client as long as the brand relationship is disclosed. The piece goes through the same review as any other, with no payment and no guaranteed placement.
Not a pitch yet?
Questions about contributing, republishing or the blog itself go through the Contact page. Want to promote PHPTRAVELS and be paid for it instead? That is the Earn with PHPTRAVELS programme, not this one.
Contact page- Hi Editorial,
- Working title:
- Audience:
- Problem we solve:
- Outline (4 to 6 points):
- Assets (screenshots, data):
- Bio, role and company:
- Brand relationship, if pitching for a client:
Also on this site
Contributor questions
Write for us: frequently asked questions
The questions contributors ask before they pitch.
Talk to salesNo. We do not sell placements, sponsor links or accept payment for publishing a piece. Every submission is accepted or declined on editorial merit, and outbound links may carry nofollow at the editor's discretion.
Yes. SaaS and B2B SaaS growth, product and marketing pieces are in scope, as are ERP, HR tech, accounting, payroll, CRM, POS and project-management topics. Travel technology and tourism SaaS remain the closest fit.
Yes, as long as the brand relationship is disclosed in the pitch. Agency-submitted pieces go through the same review, with no payment involved and no guaranteed placement.
A clear problem, a replicable approach, concrete steps and measurable outcomes. Screenshots, configs, queries and reusable checklists help; stock imagery and generic tips do not.
1,200 to 2,000 words is typical. Longer tutorials or case studies are fine when every section adds something the reader can use.
An editor replies with an acceptance, a decline or a request for a sharper angle. Accepted drafts get an editor pass and a subject-matter check, and you may receive revision notes before final acceptance.