Phaenoran has a use case deck for Bahrain, Saudi Arabia, Bali and Chennai. This plan turns each deck into six months of posts, and each post into a reason to talk.
A six month, LinkedIn led programme with a fixed monthly ceiling, built around one idea: the sea, the well and the drain are all water, and the sun can power the plant.
Phaenoran now sells a wider water offer next to solar EPC, and each market has a finished use case deck. Almost none of that thinking is public, so a buyer who has never met the team has nothing to find.
Every deck opens with a number that makes the problem plain, then maps six use cases to Phaenoran offerings. That is a ready made content spine for each market.
The website carries the company story and the new water page, but the market specific thinking lives in sales decks. A buyer cannot discover it, forward it or share it.
Factory built units delivered in 3 to 6 months, and a model where Phaenoran owns the plant and the customer buys the water, are rare in the posts buyers see today.
Source: the Phaenoran website and the Phaenoran use case decks for Bahrain, Saudi Arabia, Bali and Chennai. Market figures quoted in posts are checked against their published source before each post ships.
Get the right roles in four markets to know Phaenoran for water and solar, understand why modular works, and ask for a conversation.
Buyers connect Phaenoran with both engines, and with the idea that one team can size water and power together.
Every market sees its own numbers, schemes and use cases, so Phaenoran reads as local, not generic.
Each use case deck becomes the offer. A deck request is the first trackable step towards a workshop.
Modular delivery and Water as a Service move from a slide to a topic buyers and investors already know.
| Measure | Today | Direction |
|---|
Proposed targets. Record the LinkedIn and website baselines in Month 1 and recalibrate after one full month of data. Deck requests and enquiries are tracked on the contact form and the Lead Gen Form.
A water or solar project is chosen by a group: the owner or authority, the engineers, the developer and the financier. Every post is written for one of six audiences, never several.
| Audience | Who | What they look for |
|---|
Posts by primary audience. Every post on the calendar names the one audience it is written for.
Each market gets twelve posts, written from its use case deck. The Global track of 24 posts keeps the whole portfolio visible between market waves.
| Market | Leads in | Local timing to respect | Check before posting |
|---|---|---|---|
| Bahrain | Month 2 | Bahrain National Day on 16 December. Gulf posts run lighter from the start of Ramadan, around 8 February. | Tubli and Muharraq effluent figures are the latest published. Confirm the Hawar resort status. |
| Saudi Arabia | Month 2 | Ramadan around 8 February to 9 March. Lighter Gulf weeks in Months 4 and 5. | Capacity figures differ by source. Local content and regional headquarters claims need a confirmed route before they appear. |
| Bali | Month 3 | Winter peak season. Nyepi, the day of silence, falls in March and no post should go out that day. | Confirm the current groundwater permit enforcement position with a local consultant. |
| Chennai | Month 3 | Pongal in mid January. Republic Day on 26 January. | The large desalination contract is already awarded: write for satellite capacity, packages and operations, not the headline award. |
Ramadan and Eid dates follow the moon sighting. Confirm each date a week ahead.
One track keeps Phaenoran visible and explained in every market. The other takes each market in turn, from its first number to a discovery workshop.
Every market deck starts from a water problem, and solar is how the plant gets powered. So most posts lead with water, a good share pair it with solar, and a smaller set speak to solar alone. The mix is tracked on the calendar under each post.
Ground rules: no customer names, no tariffs, tenors or returns, and every figure checked against a source before it ships.
Each phase has one job. Each post speaks to one audience in one market.
Every post belongs to one theme, so the feed reads as one system and nothing is left to chance.
| Code | Theme | Posts | Covers |
|---|
The Phaenoran look: clear photography with space for the headline, DM Serif Text in white, the key phrase in orange, a short tag line and the mark bottom right. Short copy underneath, one call to action.
Figures to be verified against the published source before the post ships.
Written for the data centre use case in the Saudi Arabia deck.
The 3 to 6 months figure is the Phaenoran delivery range. The conventional comparison is a typical benchmark and is labelled as one.
Illustrative layouts using the AI generated market photographs from the Phaenoran use case decks. Final images are produced and approved by Phaenoran, with licensed photography where available.
At ₹25,000 a month the plan is phased. Month 1 only sets up. In Months 2 and 3 about four fifths of the month goes to the two markets that are leading, with a thin amount keeping the others warm. Months 4 to 6 spread the money evenly across the four markets. Everything runs on LinkedIn, with an optional small Instagram test for Bali hospitality.
| Month | What runs | Planned |
|---|
Planned figures are proposals inside the ceiling and leave headroom each month. Ads link to a use case deck request or the contact form, and the form submission is the conversion. Phaenoran approves every campaign before it runs. Amounts are in Indian rupees.
72 posts on a real calendar, with status, comments and spend you can track.