The cost of implementing an embedded domain specific language (eDSL) depends on the eDSL development tools used to build it, but these costs are not readily apparent at the outset. Markedly enables developers to map elements of the eDSL implementation and attach implementation costs to these elements. An implementation diverging from its design incurs four types of costs: Preserve, Extend, Adhere, and Recognize (PEAR). To illustrate the Markedly approach, we calculate the costs of example eDSLs using a map for the Haskell language metaprogramming and host language toolsets. To evaluate this approach, we will assess developers as they reason about costs while implementing an eDSL.