Midsummerr now serves audiobook studios, publisher audio teams, audio-drama producers, and localization shops with a modular production-services offering. That is the real update here. The dedicated /services page is just how we made the expansion visible on the site.
If you run a production house, the usual software pitch is all-or-nothing: move the whole workflow, replace the team, accept a new creative process. That is not how many real productions work. A lot of teams already have narrators, directors, editors, and delivery standards. What they need is a production layer that can take a specific chunk of work off the board without hijacking the whole show.
That is what this expansion is for. Studios and producers can now use Midsummerr for the part of the pipeline they want help with, keep the part they already do well in-house, and move faster without flattening the creative process.
What shipped
The expanded offering is built around four concrete services now packaged for studio workflows:
- Script mapping for character-by-character line assignment and scene-by-scene emotional arcs.
- Music and SFX cueing for productions that need the cue sheet before they need the final mix.
- Audio elements delivered either as stems or as a mixed, loudness-matched chapter.
- Dialogue assembly for separately recorded casts that need to land as one natural conversation.
Those are not hypothetical ideas or roadmap language. They are the exact services Midsummerr now offers production teams, with a direct inquiry path for studios that want to plug the pipeline into an existing production.
Ready to try it on your own book?
Start with 5,000words free →This is an expansion, not a pivot away from studios' existing process
The most important line on the page is also the simplest: you keep casting, performance, and the final master.
That is the frame of the expanded offering. This is not "give us your book and disappear." It is a modular production setup for teams that already have part of the workflow handled. If your studio already casts narrators well, you keep doing that. If your producers already own the final sound design decisions, they keep doing that. If you have a separately recorded cast and need the dialogue assembled cleanly, that is a narrower production problem, and it should be treated like one.
That same framing carries through the rest of the shipped page:
- Pronunciation control for names, places, and invented terms, tested in audio before you commit.
- Backlist and multi-title runs for teams that need consistent treatment across a catalog, not just a one-off experiment.
- Disclosure-ready positioning for teams working within platform and licensing requirements.
In other words, this is not just a new landing page for a generic AI tool. It is an expansion of the offering itself: Midsummerr can now be bought and used as part of a professional audio workflow.
Why this matters for studios and publisher teams
Studios do not usually need another homepage promising "AI audiobook creation." They need to know whether a vendor can fit inside an existing production model, what comes out the other side, and which creative decisions remain theirs.
The expanded production-services offer answers that directly, and the new /services page finally states it in the right language.
If your bottleneck is pre-production, the script-mapping offer matters. If your bottleneck is post, the audio-elements and dialogue-assembly offers matter. If you are handling a backlist, consistency matters more than novelty, and the page now says that plainly.
That matters internally, too. When an audio team shares a vendor around, the offer needs to be legible to multiple stakeholders at once: producer, editor, director, and operations lead. A consumer-facing product page usually does not do that job well. A studio-facing services offer can.
You can hear the output, not just read about it
The page does not ask studios to imagine the result. It reuses the same showcase audio already live on the site, so teams can hear the kind of production the pipeline supports. If you want the fastest calibration point, start with:
Those listening pages make the conversation more concrete. "Script mapping" and "dialogue assembly" are production terms. Hearing the resulting scenes is what tells you whether the workflow is worth evaluating for your own catalog.
Who this is for
This launch is aimed at four groups now called out directly on the page:
- Audiobook production studios
- Publishers' audio teams
- Audio-drama and immersive producers
- Localization and dubbing studios
That matters because each group tends to need a different entry point. A publisher may want repeatable backlist throughput. An audio-drama team may care more about cast assembly and cueing. A localization shop may care about pronunciation control and workflow fit. The page does not force those needs into one generic pitch.
What to do next
If your team already knows where the gap is, go to the services page and use the inquiry prompt with that exact production need. If you want to compare it to the platform side first, the features page shows the broader product workflow and the pricing page shows the production tiers behind it.
The useful shift here is simple: Midsummerr is no longer only an author-facing audiobook workflow. It now also serves production houses directly with modular production help that fits around their existing cast, team, and creative process.
FAQ
Is this a separate product from Midsummerr?
No. It is the same production pipeline, but the offering has expanded so studios and producers can buy into it directly through a service model that matches how they already work.
Does Midsummerr take over the final creative direction?
No. The shipped services page states that teams keep casting, performance, and the final master. The point is to plug into the production work in between, not replace the studio's creative ownership.
Can a studio use only one part of the workflow?
Yes. The page is explicitly modular. Teams can come in for script mapping, cueing, audio elements, dialogue assembly, or a broader engagement depending on where the bottleneck is.
