Nector — by Five Technology

Turn your team's nectar into your website's honey.

The content engine for businesses where the people doing the work are the people with the best stories. Your crew brings the nectar. Nector turns it into honey.

See it live How it works

The bee metaphor

A small vocabulary that makes the whole system intuitive — to your crew, your admins, and your customers.

Worker bees

Your crew, your photographers, your realtors. The people closest to the work.

Nectar

What they collect — raw photos, voice notes, video, a quick line of text.

The hive

the Nector platform. Where nectar gets organized, polished, and stored in the comb.

Honey

Polished, published content on the public website. Ready to attract.

Pollen

Leads and inquiries flowing back. Form submissions, organized by source.

The queen

You. One tap publishes; one tap pulls it back. Always in control.

How the hive moves

Nectar in, honey out, pollen back. Four roles, one continuous loop.

Worker bee phone in the field NECTAR photo · voice · video · text NECTOR the comb organize · polish · store ♛ queen approves HONEY published portfolio entry Public site visitors · buyers · leads POLLEN inquiries · form submits · leads
Worker bees bring nectar → Nector organizes → queen approves → honey on the site → pollen back.

What breaks without Nector

Most CMSes are built for desktop publishers. The people who actually have the content never touch them. So…

 Content backs up in email

"Hey, can you send me those photos?" Three weeks later, still in someone's inbox.

 Photos die on a phone

Snapped, never unloaded. The website never knows the project happened.

 Nobody owns it

Is it marketing's job? The PM's? The agency's? While it's debated, nothing ships.

 The website drifts

Stale photos. Old projects featured. Prospects wonder if you're still in business.

How it works

Photos from the truck. Live on the site by lunch. Five steps, both ends measured in seconds.

1

Open the app on a phone

No password — magic link by email or text. Installed once, opens like any other app, stays signed in for 90 days.

Sign in screen on iPhone
2

Name the job, snap the photos

"Lake Home — Maple Plain." Pick from the gallery or shoot right there. Up to 25 photos per upload, EXIF auto-rotated, web-sized automatically.

Upload form with camera and gallery options
3

Tap send

Photos resize, organize, and turn into a draft project inside Nector. The bee's done. They go back to work.

4

Queen reviews

Admin opens "Publish" on phone or desktop. Scrolls drafts, taps the eye icon to flip live. Drags to reorder. Opens the live site in a new tab to verify.

Publish admin showing live and draft project lists
5

Honey on the website

Site updates immediately. Real photos. Real job name. SEO-ready, retina-sharp, mobile-fast.

Full project preview modal showing every photo

The Gallus story

Gallus Homes builds custom barndominiums and lake homes in Minnesota. Before Nector, photos lived in someone's inbox for weeks before going up — when they made it up at all.

The crew finishes a project, takes a few pictures on a Tuesday afternoon, the website shows it Wednesday morning. No agency in the middle. The superintendent uploads from his truck. The owner approves over coffee. The new project hangs on the homepage by lunch.
— what changed after switching to Nector

See the Gallus site

Nector vs. most CMSes

Not better at the same thing. Better at a different thing.

Most CMSesNECTOR
Built forDesktop publishersField crews + admins
Default deviceLaptopPhone
Friction to add contentLogin → tree → form → upload → save → publishTap → photos → tap
Friction to approveSame as aboveOne tap, either device
Photo handling"You figure out the thumbnail"Auto resize · EXIF rotate · variants
ExtensibilityPlugins inside a boxFramework — write what you need
Where the team livesEmail + Slack threadsThe hive

Share-ready copy

Pre-sliced for the platforms that matter. Each card copies clean.

X / Twitter

280 chars
Your crew has the content. Nector has the comb. Field → photo → tap → live website. 10 seconds each end. No tickets. No email threads. No agency middleman. See it: gallus.fivetechsites.com

LinkedIn

~700 chars
Most CMSes are built for desktop publishers — a laptop, a tree of menus, a form to fill in. The people who actually have the content (your superintendent, your photographer, your realtor on a showing) never touch it. So content backs up. In email. On somebody's phone. In a Slack thread that's three weeks old. Nector flips the model. Worker bees bring the nectar — raw photos from the field, in 10 seconds, from their phone. Admins turn it into honey on the public website with a single tap. The site stays as current as the work, because the cost of feeding it is near zero. Live demo: gallus.fivetechsites.com

Cold email

subject + 3-line opener
Subject: photos from the truck, live by lunch Most CMSes are built so somebody at a desk uploads what your crew did last week. We built one for the opposite: your superintendent snaps three photos on a job site, taps send, and the website updates that afternoon. Worth a 15-minute look? Live example: gallus.fivetechsites.com

Instagram caption

with hashtags
Built for businesses where the people doing the work are the people with the best stories. 🐝 Worker bees bring the nectar — photos from the job site, in 10 seconds, from their phone. The hive turns it into honey on the public website with a single tap. No tickets. No email threads. No agency middleman. See it live → link in bio. #webdesign #cms #constructiontech #realestatetech #fieldservice #smallbusiness #mnbusiness #fivetechnology #hive