HDS: Plan of Action

Build phase

What needs to be in good shape before the September meeting with Piteå Kommun. Ordered by dependency: the redesign check comes first because its answer changes what else needs doing.

Check first Understand the redesign directory

Open /public_html/redesign/ (subdirectories a, b, c) and establish what phase it is in: early prototype, active development, or abandoned. This determines whether the coordinator-facing UI being shown in September is the current build or the redesign. Piteå's digital coordinator should not demo a version that is mid-rebuild.
Decide: freeze the redesign until after September, or accelerate it to be ready. Pick one. Document the decision here.

Platform polish Field agent system and sample pages

Walk the entire field agent flow as a new user (log in cold, find a business, submit it, edit it, find it in the map view). Fix anything that breaks or requires explanation. If a Koler Intresseförening volunteer cannot do it alone, it is not ready.
Get sample-nasaleden.html to a showable state. Currently not linked in outgoing materials because it is not ready. It is a key proof-of-concept page. Unblock it.
Fill the gaps in the Piteå subdomain portal: events, entity profiles surfacing publicly, and the notice board are currently absent from pitea.hittadittsverige.se.

Entity activation Get real claimed profiles into the catalog

Book and run an entity activation day with Cathrin Elfstrand at Norrskensgården, Långträsk. This was already identified as the first candidate (~8,000 SEK activation day). One real claimed profile changes the catalog from a data list to a working directory. Several more changes the story entirely.
Target at least 3–5 claimed, well-populated profiles live before the September meeting.

The political sale

Independent review, point 4. This is the most important strategic note in the document. Read it before the September meeting.

External review finding

You are selling a technology product to people who need a political cover story.

By the time a 200,000 SEK/year contract gets approved, it has passed through a kommunstyrelsen or equivalent body where the people voting are elected councillors, not digital strategists. Those people are not evaluating features. They are asking: can I defend this spend publicly? Does this look like a good use of taxpayer money? What happens if it fails and it ends up in the local paper?

The platform documentation leads with architecture, feature count, and SLA clauses. That is the right language for a procurement officer doing due diligence. It is the wrong language for the room where the decision actually gets made.

The technical sale may already be won. The political sale is a different animal.

The narrative councillors need

This story exists in the platform. It needs to be handed to Maria in a form she can carry upward, not left buried in technical docs.

Political language for the room where the decision gets made

Piteå's villages go on the map: findable, visible, and representative of what is actually there
Local businesses and associations get a digital presence they could not afford to build themselves
Rural life becomes more visible and connected, which is a direct response to depopulation pressure
The data belongs to Piteå, is managed locally, and stays in Swedish infrastructure
Piteå is the founding partner: its experience shapes the platform for every commune that follows

What to do before September

Single most important conversation

Ask Maria: "What does your boss need to hear to approve this?"

Do not assume the answer. Maria is the internal champion. She knows what Ulf Fjällström and the kommunstyrelsen will push back on. Get that information directly and prepare accordingly. The product docs handle the procurement layer. Maria handles the political layer. Give her the language to do that.

Political prep Equip Maria before the September meeting

Ask Maria what her boss needs to hear. Do this before the meeting, in a follow-up to the email sent August 13. Frame it naturally: "Before we meet, it would help me to know what questions you expect from your side so I can make sure we cover the right things."
Prepare a one-page political narrative (not a feature list) that Maria can share with Ulf or take into a kommunstyrelsen briefing. Focus on the village story, not the platform architecture.
In the September meeting: spend the first 10 minutes on outcomes and the Koler story before touching any screen. The demo is evidence; the story is the sale.

Where things stand

Piteå account status as of August 2026.

Email sent August 13 to maria.oberg@pitea.se, CC ulf.fjallstrom@pitea.se. Four document links, platform link, survey reference, office visit request.
Follow-up: ask Maria what her boss needs to hear.
September meeting confirmed and date set.
In-person: tourism team, business developer, digital coordinator introductions.
Contract discussion with Ulf.
Founding partner agreement signed.