tags. Let's draft: Lead paragraph: Bitdeer has signed a $400 million agreement to provide AI cloud computing services from a facility in Malaysia. The five-year deal is expected to start bringing in revenue in early 2027. The company is also working toward 350 megawatts of AI cloud capacity by 2028. Then subhead: "The $400 Million Agreement" - but that's a bit generic. Maybe "A Five-Year Commitment" or "What the Deal Means for Bitdeer" - but we don't know specifics. Let's do "The Deal's Timeline" or "Revenue Starting in 2027" - that's specific. I'll write: Revenue Expected in Early 2027
The agreement, which runs for five years, will see Bitdeer deliver AI cloud computing services from its Malaysia facility. The company hasn't said exactly when the contract was signed, but it expects to begin recognizing revenue from the deal in early 2027. That leaves a gap of more than a year before the first payments flow, suggesting the facility is still being built out or that services will ramp up gradually.
Then another subhead: "Building Toward 350 Megawatts" - that's specific.Building Toward 350 Megawatts
Bitdeer has set a target of 350 megawatts of AI cloud capacity by 2028. The Malaysia deal is part of that broader expansion. The company has been adding data center capacity across several regions, though this particular agreement ties a significant revenue stream to one location. The 350-megawatt goal would put Bitdeer in a position to handle large-scale AI workloads, a market that's grown quickly as companies race to deploy machine learning models.
But careful: we cannot say "companies race" or "market grown" if not in facts. We must stick to facts. So we need to avoid adding external context. We can only say what's in the facts. So we can say: "Bitdeer has set a target of 350 megawatts of AI cloud capacity by 2028. The Malaysia deal is part of that broader expansion." That's fine. We can also say "The company expects the capacity to be in place by 2028." No extra. We need to vary sentence length. Also avoid clichés. Let's write a second paragraph for that section: "The company hasn't detailed how much of the 350 megawatts will be used for this specific contract. The deal's revenue won't start until 2027, so the buildout may be timed to that schedule." We need to be careful not to speculate. We can say "The company hasn't detailed..." but that's not in facts. Actually facts don't say that. We can only say what we know. So we can say "The company has set the 350-megawatt target for 2028, and the Malaysia facility is part of that plan." That's it. Let's write the content more naturally. Maybe we have a third section about the significance of the deal? But we don't have any context. We can say "The deal is one of the larger AI cloud contracts for the company, though Bitdeer hasn't disclosed other similar agreements." That's speculation. We can't say that. Better to keep to what we know. We have three facts: deal amount, duration, revenue start, capacity goal. So we can have sections: The deal, the timeline, the capacity goal. Or we can combine. Let me write: Lead: Bitdeer has signed a $400 million agreement to provide AI cloud computing services from a facility in Malaysia. The five-year deal is expected to start generating revenue in early 2027. The company is also working toward 350 megawatts of AI cloud capacity by 2028. Then a section: "A Five-Year Contract" - but that's too short. Maybe "The Malaysia Facility Deal" - but we don't know facility details. Let's do "What the Deal Covers" - but we don't know specifics. We only know it's AI cloud computing services. So we can say: "Under the agreement, Bitdeer will provide AI cloud computing services from its Malaysia facility. The contract runs for five years. The company hasn't said which clients will use the services or what types of AI workloads will be handled." That's not in facts. We can't say "hasn't said" because we don't know if they said. We can say "The company has not disclosed further details about the services." That's also not in facts. We can only state what we know. So we can say: "The agreement covers AI cloud computing services to be delivered from a facility in Malaysia. The contract's term is five years." That's it. Maybe we can have a section "Revenue Starts in 2027" and another "Capacity Target of 350 MW". That's enough. Let's write:Revenue Starts in 2027
The deal won't produce revenue until early 2027. That's more than a year away from now. Bitdeer hasn't explained why the revenue recognition starts so late, but the timeline suggests the Malaysia facility is still being equipped or that the services will be phased in. The five-year term means the contract would run through at least 2032.
But careful: we don't know "now" date, but we can say "more than a year away" if we assume current date is 2025? Actually we don't know. The facts say "expected to begin in early 2027". We can say "The company expects revenue to begin in early 2027." That's fine. We can say "That leaves a gap of more than a year from the announcement, though the exact signing date wasn't disclosed." But we don't know announcement date. So we just say "The company expects revenue to begin in early 2027, which is more than a year after the agreement was signed." But we don't know when it was signed. So we should avoid that. Let's stick to: "Revenue from the agreement is expected to begin in early 2027." Then we can say "The five-year term would stretch into 2032." That's a simple calculation: five years from 2027 is 2032. But careful: five-year deal, revenue begins in 2027, so the deal might start then. So we can say "If the revenue starts in 2027, the five-year contract would run through at least 2032." That's logical but is it inventing? It's a factual calculation from the facts. We can say "The contract's five-year term would extend through early 2032 if revenue starts as expected." That is a reasonable inference but not explicitly stated. We can phrase it as "The five-year term, combined with the 2027 start, would put the contract's end date around 2032." That might be too speculative. Better to avoid. We can say "The company has not said when the five-year period begins." That's not in facts. Actually the facts say "The agreement is a five-year deal." and "Revenue from the agreement is expected to begin in early 2027." So we can say "The revenue stream is expected to start in early 2027, and the contract runs for five years." That's all. Let's write a more natural piece. I'll draft the full content:Bitdeer has signed a $400 million agreement to provide AI cloud computing services from a facility in Malaysia. The five-year deal is expected to start generating revenue in early 2027. The company is also working toward 350 megawatts of AI cloud capacity by 2028.
A Five-Year Agreement
The deal, valued at $400 million, covers AI cloud computing services delivered from Bitdeer's Malaysia facility. The contract runs for five years. Bitdeer hasn't disclosed which clients will use the services or what specific AI workloads will be supported.
The agreement is part of Bitdeer's push into AI cloud services, a segment the company has been expanding. The Malaysia facility is one of several data center projects the company has underway, though this particular contract ties a large revenue stream to that location.
But we cannot say "has been expanding" or "several data center projects" because that's not in facts. We only have the facts given. So we must stick to what we know. So we can say "The agreement is part of Bitdeer's AI cloud services business." That's fine because it's implied. But we can't say "push into" or "expanding" as it's not stated. We can say "The agreement adds to Bitdeer's AI cloud computing offerings." That's also not stated. We need to be minimal. Let's just state the facts. Better structure: Lead paragraph with all key facts. Then a section "Why the Revenue Starts in 2027" but we don't know why. So we can't have that. We can have a section "Capacity Goal by 2028" which is a fact. Let me write:Capacity Target of 350 Megawatts
Bitdeer has set a target of 350 megawatts of AI cloud capacity by 2028. The Malaysia facility is part of that plan. The company hasn't said how much of that capacity will be dedicated to the $400 million contract, but the revenue from the deal is expected to start in early 2027, before the 2028 target date.
That is logical but we don't know if the facility is part of that plan. Actually the facts say "Bitdeer is building toward 350 megawatts of AI cloud capacity by 2028." It doesn't explicitly say the Malaysia facility is part of that, but it's reasonable to assume. But we should avoid assumptions. We can say "The company's overall goal is 350 megawatts by 2028." and "The Malaysia deal is separate from that." Actually we don't know. So we can state both facts without connecting them: "Bitdeer has also said it is building toward 350 megawatts of AI cloud capacity by 2028." That's fine. Let me write the article with two subheads: "Revenue Timeline" and "Capacity Buildout" but we need story-specific. How about: "The $400 Million Contract" and "The 2028 Capacity Goal" - that's specific. I'll do:The $400 Million Contract
Bitdeer has signed a five-year agreement to provide AI cloud computing services from its Malaysia facility. The total value is $400 million. Revenue from the deal is expected to begin in early 2027. The company hasn't given a reason for the delayed start, but the contract's length means the services will run for several years once they begin.
The 2028 Capacity Target
Separately, Bitdeer is building toward 350 megawatts of AI cloud capacity by 2028. That target includes data center projects in multiple regions, though the company hasn't broken down how the capacity will be distributed. The Malaysia facility is among the projects that could contribute to that number.
But we can't say "could contribute" because that's speculation. We can say "The company has set a target of 350 megawatts by 2028." and then "The Malaysia deal is part of its AI cloud business." That's fine. Let me rephrase to be strictly factual. Actually, we have no info about other regions. So we can't say "multiple regions". We can say "The company has set a target of 350 megawatts of AI cloud capacity by 2028. The Malaysia facility is one of the sites that will host that capacity." But we don't know if it will host that capacity. We only know the deal is for that facility. So we can say "The company is also working toward a 350-megawatt AI cloud capacity target by 2028." and leave it at that. Maybe we can have a section that discusses the deal's significance in terms of revenue timing. But we don't have any other deals. Let me write a concise article. I'll have a lead, then two subheads: "A Five-Year Deal" and "Capacity Goals" but that's not story-specific enough. Let's do "Revenue Starts in 2027" and "350 Megawatts by 2028" - those are specific facts. I'll write:Bitdeer has signed a $400 million agreement to provide AI cloud computing services from a facility in Malaysia. The five-year deal is expected to start generating revenue in early 2027. The company is also working toward 350 megawatts of AI cloud capacity by 2028.
Revenue Starts in 2027
The deal's revenue stream won't begin until early 2027, more than a year from now. Bitdeer hasn't said why there's a delay, but the timeline suggests the facility is still being equipped or that services will be phased in gradually. The contract runs for five years, meaning it could stretch into 2032 if the start date holds.
That last sentence is an inference. We can say "The five-year term would run through at least 2032 if revenue starts as planned." That is a simple calculation. But we don't know if the term starts at revenue start. It might start earlier. So we should avoid. We can just say "The contract runs for five years." and leave it. Let me rephrase: "The deal runs for five years. Revenue is expected to begin in early 2027." That's it.350 Megawatts by 2028
Bitdeer has set a target of 350 megawatts of AI cloud capacity by 2028. The Malaysia facility is part of that broader buildout, though the company hasn't said how much capacity will be dedicated to the $400 million contract. The revenue start in 2027 suggests the facility will be operational by then, ahead of the 2028 capacity goal.
Again, "suggests" is speculation. We can say "The revenue start in 2027 is before the 2028 capacity target." That's a fact. We can end with: "The company expects to reach the 350-megawatt capacity by 2028, and the Malaysia deal is one piece of that plan." But we don't know if it's a piece. We can just say "The company expects to reach 350 megawatts by 2028." and then "The Malaysia deal is separate." Actually we can combine: "Bitdeer is building toward 350 megawatts of AI cloud capacity by 2028. The $400 million Malaysia deal is part of that effort." That's reasonable, but we don't have explicit link. The facts say "Bitdeer signs a $400 million AI cloud computing deal for a Malaysia facility." and "Bitdeer is building toward 350 megawatts of AI cloud capacity by 2028." It's plausible that the deal contributes to that, but we can
