Blueprint by Tiny
Return to Tiny.cloud
Return to Tiny.cloudTry TinyMCE for Free
Search by

Building a rich
text editor is expensive

Buy vs build cost blowouts


Do we buy, or
do we build?

It’s a familiar question…

that arises in almost every development project,
no matter the size.

Rich Text Editors (RTEs) are one of the highest-risk areas
for both cost and development time overruns.


$29,425,179

Wolfram & Hart


$22,314,689

Montgomery Burns


$19,893,421

Baxter Stockman


$15,368,729

Globex

Four companies* who decided to build their own
core rich text editor in-house, paid dearly for their decision.

How did they get that $ price tag?

Some enterprises still persist in believing they need to build their own… everything.


Just

37%

of organizations say IT completed
all their projects*


fewer than

4 IN 10

teams

fulfil their project commitments
to business stakeholders++


$1,178,921^

development cost for an advanced
copy-past feature


8.9

person-years to build an advanced copy-past feature


$10M — $30M+

development cost for
a basic rich text editor


71 — 128

person-years to build a basic rich text editor


Transformation and speed-to-market have made the old belief, in custom-building all your own technology, redundant. Neither budget, nor developer resources, are elastic.

What’s the answer?


Buy vs Build isn’t
the conundrum

It’s how you build everything you need…
at scale

A more agile approach is to assemble rich text editor components into a flexible, reusable tech stack.

Either… buy an out-of-the-box RTE or utilize an open source core that your dev team can use as a framework for customization and support it with advanced feature plugins.
You then get the best of everything

Using a buy-and-assemble component approach for your rich text editor

Minimizes custom-build

outside your expertise


Facilitates

continuous deployment of software


Maximizes dev talent

who pick the exact tools needed


That’s how you get products faster-to-market at a smaller
price tag

Get more insights in our
Buy vs Build White Paper

Download the White Paper

In a rush?

Download the ‘Building a rich text editor is expensive’ Infographic and read it later

Footnotes:

*Company and personal details are fictional, but indicative of the costs and time taken to build a functioning rich text editor.

++ Mulesoft 2021 Connectivity Benchmark Report

Open Hub estimate of the cost of building the basic open source components of three leading rich text editors (excluding advanced features and plugins)

^ Using a normalized COCOMO Model, the estimated engineering requirements for building a single advanced feature

Sources:

The Great Debate: Buy vs Build Rich Text Editors

Buy vs Build: Clean copy-paste feature cost estimate

COST ESTIMATE CURRENCY
All cost estimates quoted are in US$

TinyMCE

The rich text editor behind great content creation experiences

Related Articles

  • Product-Led Growth

    ECM vs DMS vs KMS: what's right for you?

    by Di Mace in Product-Led Growth
Subscribe for the latest insights served straight to your inbox every month.

Deploy TinyMCE in just 6 lines of code

Built to scale. Developed in open source. Designed to innovate.

Begin with your FREE API Key
Tiny Editor
Tiny logo
Privacy Policy - Terms of Use© 2022 Tiny Technologies Inc.TinyMCE® and Tiny® are registered trademarks of Tiny Technologies, Inc.

Products

  • TinyMCE
  • Tiny Drive
  • Customer Stories
  • Pricing