The Village of Lindenhurst
already does all of this by hand.
On 9 November 2026 we sat with the Village of Lindenhurst’s staff for fifty-three minutes and showed them Municiply. What follows is drawn from that recording. It separates four things that are easy to blur together: what the village described, what we demonstrated, what has actually been built, and what has been observed in use.
Nothing here is a results claim. At the time of writing the village has not adopted Municiply, no Municiply content has published on its behalf, and no outcome has been measured. If that changes, this page changes with it.
The writing was never
the hard part.
Every line in this section is the village’s own words from the recording. Speakers were not individually identified in the transcript, so quotes are attributed to village staff rather than to a named person.
They were already the production department.
Not a theory about small municipalities — a description of their Monday.
“At this point we were making our own flyers. We were doing everything.”
Village staff · 34:38
“I’m doing it on my Canva.”
Village staff · 34:44
The creative part is fine. The routine is the burden.
This distinction mattered, and it shaped what we did and did not propose to replace.
“That part of it I really don’t mind. It’s like fun to be creative in that way, but … this is like the burden.”
Village staff · 35:15
The calendar already exists. It just goes nowhere useful.
They maintain a Google Calendar and send it to the people who do their social media. The source of truth was never the problem.
“We have a Google calendar that we send out to our social media team now … so that part of it’s already done. It’s not like it would be adding additional work on to us.”
Village staff · 26:38
Residents call, and get put on hold.
Asked what a resident does today when they cannot find something:
“They eventually have to call us, still be put on hold.”
Village staff · 37:44
They had a photo problem with a date on it.
Unprompted, staff described a specific annual need: collecting residents’ photographs for the screen at the village’s New Year’s Eve event.
“We try and get people to send us photos … and we were trying to come up with an easy way that people can just like upload it to some sort of system without having to email it to us or send it in a message, and then we have to save it and pull it from there.”
Village staff · 36:22–36:41
And a gap we cannot close.
Asked directly what would be missing, staff named the one thing their current arrangement gives them that Municiply does not.
“The ability we currently have with our social media people to be like, hey, we can’t make it to this event — can you go and can you film this and can you take photos? We need drone footage.”
Village staff · 29:52–30:03
Municiply does not send anyone to photograph or film. It was said in the room and it is said on this site: if on-site production is part of what a municipality buys today, it still needs it. Resident-submitted content and a village’s own photo library are a different answer, not the same one.
Shown on screen.
Not the same as delivered.
These are the parts of the product the village saw working during the session. A demonstration is evidence that something exists, and nothing more.
An event becoming a post prepared for review, with a photograph attached from a library rather than hunted for.
Content waiting for a person, and the point that nothing moves to a public channel without one.
Shown in response to their interest in what survives when a post is taken down. Capture is automatic for what Municiply publishes; it does not reach activity performed directly on a platform.
Subjects, sources, wording and the pause control — the staff-facing side of the resident assistant.
The reaction on the record, from village staff at 30:09: “From a like overall management perspective, I mean this is wonderful. It’s simple. It’s easy to go from one place.” That is a response to a demonstration. It is not a statement about results, and we are not going to present it as one.
Two different
pieces of work.
Efferent Media rebuilt the Village of Lindenhurst’s website and resident assistant. That is a separate engagement from Municiply, and conflating the two would make this page say something untrue.
A rebuilt municipal website and a resident assistant trained on the village’s own published documents. Village staff received their own logins on 10 November 2026.
During the session staff asked whether a rotating notice could sit at the top of every page, for things like a tax deadline. It was built the next day. On the village website. It is not a Municiply feature and does not demonstrate one.
Municiply was presented, priced and left with the village to take to its board. No Municiply content has been published for Lindenhurst and no Municiply channel is connected on its behalf.
Staff asked how to share one event twice a week in the run-up. The honest answer in the room was that it needed building. It is recorded here because a question a prospective customer asks that we cannot yet answer is worth more to the next village than another feature we can.
Nothing yet.
And that is the honest answer.
There is no adoption to report, no published volume, no reach figure, no time saving and no resident response. A municipal communications product that showed you numbers at this stage would be showing you numbers it made up.
What exists is a detailed account of what one village said it needed, and a product built against those needs that can be checked line by line against what is available today.
Source: a 52-minute 59-second recording of the session on 9 November 2026, transcribed locally. Quotes are verbatim from that transcript with filler removed where it does not change the meaning; timestamps refer to the original recording. The transcript notes that speakers were not individually identified, so no quote on this page is attributed to a named person. An internal evidence note records the source passage for every claim above.
Your village is probably doing this by hand too.
Bring the calendar you already keep and the questions your office answers most. We will be as specific about what Municiply does not do as about what it does.