# Pineland Technologies > Websites and custom solutions for small businesses, built properly and looked after for years. Pineland Technologies builds websites for small businesses in Cedar Rapids, Iowa and across the United States: designed for the business, fast on a phone, set up to be found, and hosted and looked after on a flat monthly plan by the people who built them. Every site passes all nine of our AI-friendly checks the day it launches. When a business outgrows its website we build the software behind it too: booking systems, customer portals, mobile apps and operations consoles. Building for the web since 2014. Based in Cedar Rapids, Iowa. Working remotely with clients across the United States. Operating under this name since 2014. Every website we build is written for two readers: the search engine, and the assistant that answers instead of it. Each one publishes a file like this one, generated from its own content and pointed at from its robots.txt, so a question about the business is answered from the business. The practice, and the evidence that almost nobody else does it, is at https://pinelandtech.com/ai-friendly. ## Contact - Email: hello@pinelandtech.com - Phone, text preferred: (319) 677-1313 - Website: https://pinelandtech.com - Contact form: https://pinelandtech.com/contact - Office: 842 Vernon Valley Dr., Ste. 5, Cedar Rapids, IA 52403 - Coverage: Working remotely with clients across the United States. - Working on the web since: 2014 Email is the way in, and a text to (319) 677-1313 is preferred to a call. The office is at 842 Vernon Valley Dr., Ste. 5, Cedar Rapids, IA 52403, and most of the work is done remotely with clients across the United States, so email before stopping by. ## What we do The list is short on purpose: 5 services, and everything on it has shipped to production more than once. ### Websites Websites for small businesses: fast, found, and easy to change. Most of what a small business needs from its website is simple and easy to get wrong. It has to open fast on a phone, show up when somebody searches for what you do, and make calling or booking the obvious next step. We design each site for the business it belongs to rather than from a template, and build every page ahead of time so it is served from a CDN with nothing to wait on and nothing to patch. The content lives in one place, so changing a phone number is one edit, not thirty, and every site passes all nine of our AI-friendly checks the day it launches. Then we host and watch it on a flat monthly plan, because a site nobody is watching is a site that goes down on a Saturday. What that includes: - A design made for your business, in its own look, not a template with your logo on it - Every page prerendered and served from a CDN, so it opens fast on a phone - Search done properly: titles, sitemaps, structured data, and all nine AI-friendly checks - Location and service pages driven by one data file, so a new town is one line - Migration from WordPress, Wix, Squarespace, or a rented template, with old links kept working - Hosting, monitoring, and content updates after launch, on a flat monthly plan - A back office at /admin: your traffic, your invoices, and a request form that reaches a person Evidence: 14 projects at https://pinelandtech.com/work/websites On the site: https://pinelandtech.com/services#websites ### Custom software & SaaS Multi-tenant platforms, client portals, and internal tools. When the business logic stops fitting in a spreadsheet, it needs a real application: a schema that models the actual domain, authentication that holds up, and integrations with the systems already in use. Built multi-tenant from the schema up when the product serves more than one customer, because retrofitting tenancy later is a rewrite. What that includes: - Domain modeling and schema design before any interface work - Multi-tenant architecture with enforced row scoping - Authentication, roles, and permissions, hosted or self-managed - Third-party API integration with mock fallbacks for local development - Admin consoles, review queues, and the operational surfaces nobody demos but everybody uses Evidence: 5 projects at https://pinelandtech.com/work/software On the site: https://pinelandtech.com/services#software ### Mobile apps iOS and Android from one codebase, sharing your existing backend. React Native and Expo, pointed at the same API and the same authentication as the web application, so a user who signs up on the web logs straight in on the phone. Over-the-air updates ship fixes without waiting on a store review. What that includes: - Shared authentication with the web app, no second account system - Native secure storage for tokens: Keychain and Keystore - Push notifications and deep links into specific screens - Crash reporting and over-the-air update channels - Store submission for both platforms Evidence: 2 projects at https://pinelandtech.com/work/mobile On the site: https://pinelandtech.com/services#mobile ### Custom solutions The piece you are missing, added to what already works. Not every job is a rebuild. Sometimes the site is fine and what is missing is the half nobody can see: the console that runs the crews, the booking widget that belongs on the page you already have, the attribution layer that says which ads produced work. These get built against the running system and shipped into it, and the ones that more than one client needs live in a shared block so a fix lands everywhere at once. What that includes: - Operations consoles: crews, routes, receivables, payroll, and the alerts that fire when a number moves - Embeddable widgets that drop into a site built by somebody else, themed to its brand - Ad attribution and spend reporting joined to real booked revenue - A shared blog and newsroom block, installed per site and upgraded from one place - Integrations with the software already in use, rather than a replacement for it Evidence: 4 projects at https://pinelandtech.com/work/custom-solutions On the site: https://pinelandtech.com/services#custom-solutions ### AI systems Model-backed features that hold up outside the demo. An AI feature is easy to prototype and hard to ship, because the failure modes are quiet. The work is in the surrounding engineering: constraining what the model is asked to do, validating what comes back, and deciding what happens on the path where it gets it wrong. Built to degrade into something useful rather than something confidently incorrect. What that includes: - Content generation and drafting pipelines with human review before publish - Classification, extraction, and enrichment over existing business data - Retrieval over your own documents, so answers cite something real - Structured output with schema validation rather than parsed prose - Cost, latency, and fallback behavior treated as design requirements On the site: https://pinelandtech.com/services#ai-systems ## Built for search, and for the assistants that answer instead of it An assistant asked who does a thing in a place looks for the shortest trustworthy account of a business it can find, and the address it tries first is /llms.txt. Every site we build publishes one, the way this site does, and every one of them follows the same seven practices: 1. **Every fact lives in one place.** One content source per site, read by every page, the structured data and llms.txt. 2. **An llms.txt that is a route, not a file.** /llms.txt rendered from the content source, never a hand-typed file in a public folder. 3. **Pointed at from robots.txt, listed in the sitemap.** robots.txt with a Sitemap line, an llms.txt pointer and the assistants' crawlers admitted by name; a sitemap generated from the same page list. 4. **Structured data from the same source.** JSON-LD for the business, its services, its products, its questions (FAQPage) and its breadcrumbs, generated from the content rather than typed in. 5. **Pages a machine can read without rendering them.** Static generation with semantic headings, alt text on every image, and no text set as an image. 6. **Verified on the live address, not in the code.** A build check that fails without the file, and a live check after each deploy that reads what was served. 7. **Nothing about AI on your site.** No AI copy anywhere on a client site. The file speaks about the business only. Underneath that it is an ordinary strong website, which every one of ours also is: - Every page prerendered and served from a CDN, so it opens before a visitor decides to leave - Lighthouse 90 or better on performance, accessibility, best practices and SEO, on a phone, before launch - A share card on every route, so a link pasted into a text or a feed shows the page and not a blank - A rebuild keeps the old addresses, with redirects mapped, so the pages you already rank for stay ranked - Search Console and analytics set up at launch, with the sitemap submitted, so the first crawl is on purpose - A real 404 in the site's own design that hands a lost visitor the next best page We measured three whole markets to see who else does this, by fetching robots.txt, /llms.txt and the home page on every site in the set and reading every body that came back. Across all three, 341 businesses were fetched, 19 published a file that is about the business, and 0 pointed at it from robots.txt. Two of the three are trades markets, 281 businesses in all, scored against the nine checks below; 4 of them carry a phone number, a place and a price or the opening hours in the file, and 0 pass all nine, which is what AI-friendly means on this site. Sorted by what built the site: WordPress, with an SEO plugin, 137 sites, 36 with a file, 4 about the business; Duda, 41 sites, 41 with a file, 1 about the business; Wix, 10 sites, 10 with a file, 0 about the business; GoDaddy Website Builder, 9 sites, 6 with a file, 3 about the business; Squarespace, 11 sites, 1 with a file, 1 about the business; Custom, or could not tell, 66 sites, 12 with a file, 7 about the business; Shopify, Webflow and others, 7 sites, 3 with a file, 1 about the business. The written-up study, with the method, the platform table and the four businesses that pass: https://pinelandtech.com/studies/ai-friendly-trades-2026-09-17.pdf (PDF, 9 pages). ### How to check whether a website is AI-friendly, AI-searchable, or visible to ChatGPT, Claude, Perplexity and Gemini Type the address into the free checker at https://pinelandtech.com/score-my-site. It fetches the home page, robots.txt and /llms.txt, runs the nine checks below, and shows each one with what it found, the first lines of the file an assistant reads at that address, and where the score sits against the 281 trades businesses in the study. About ten seconds, nothing stored, no sign-up. It answers the same question under any of its names: is my website AI-friendly, is my site AI-searchable, does ChatGPT see my website, how do I show up in AI answers, do I have an llms.txt, is GPTBot allowed in my robots.txt, how do I get quoted by an assistant, answer engine optimisation, generative engine optimisation. A site passes when all nine checks pass; none of the 281 did, and every site Pineland builds does on the day it launches. The nine checks, and what the trades markets scored against each: 1. **robots.txt answers, in plain text.** The address every crawler tries first returns a text file rather than an error or a styled page. Twenty-eight sites across the two markets have no usable one: eleven answer 404 with a full HTML error page, seven answer 200 with an empty body, and the rest refuse the request or never connect. Iowa trades: 141 of 157. US trades: 112 of 124. 2. **The assistants are not blocked.** Nothing in robots.txt shuts out the crawlers that read for ChatGPT, Claude, Perplexity, Gemini and the rest, whether by name or by a blanket rule. Three sites block one by name. One of them shuts out the two agents that fetch a page because a person just asked a question about it, which is a customer standing at the door. Iowa trades: 156 of 157. US trades: 122 of 124. 3. **They are admitted by name.** The file names them: GPTBot, ClaudeBot, PerplexityBot, Google-Extended and the others, each with its own group. A wildcard admits them too, so this changes nothing about what is fetched. It states a position that can be read, and its absence reads as not having thought about it. Iowa trades: 9 of 157. US trades: 8 of 124. 4. **The sitemap is declared.** A Sitemap line in robots.txt, so a crawler on a budget is handed the list of pages instead of guessing at them. This is the oldest rule here and still the one most often missed. Iowa trades: 119 of 157. US trades: 99 of 124. 5. **robots.txt points at the llms.txt.** There is no directive for it, so it is a comment on its own line after the sitemap. Not one site in either market carries it, including every site that has gone to the trouble of publishing a file. Iowa trades: 0 of 157. US trades: 0 of 124. 6. **/llms.txt answers with a real body.** A 200, plain text, and something in it. Two Iowa sites answer 200 with zero bytes, which passes every check that stops at the status line, and twelve more hand back a web page with a stylesheet on it. Iowa trades: 64 of 157. US trades: 45 of 124. 7. **The file is the business, not the sitemap.** It reads as an account of the business rather than a list of its own page links: no generator's credit on the first line, no builder placeholders, no staging domain, and under 50 KB, which is the point past which a model stops reading. This is where nearly every file that exists falls over. Iowa trades: 8 of 157. US trades: 9 of 124. 8. **It carries the facts a buyer asks for.** How to reach you, where you are, and what it costs: the three things somebody is asking the assistant for when your name comes up. Each one is read as the true answer rather than as a format, because a business can lack any of them honestly. A phone number, or an email address, or the contact form. A street address, a ZIP code, the city and state you work from, or the area you serve. A price, the opening hours, or the fact that there is no price to publish. What fails the check is silence, because a file that answers nothing gets answered from somewhere else. Four of the 281 businesses have all three in the file. Iowa trades: 1 of 157. US trades: 3 of 124. 9. **The page says the same thing in structured data.** JSON-LD on the home page describing the business, with a way to reach it in the record, so the older reader and the newer one are handed the same thing. A telephone, or a contact point for a business that publishes no number. A quarter of the set publishes no structured data of any kind. Iowa trades: 62 of 157. US trades: 67 of 124. - Iowa trades: plumbers, electricians, HVAC, roofers, detailers and eighteen more: 157 sites fetched on 17 September 2026. 64 answered at /llms.txt (41%), 8 published a file that is about the business rather than an index of its own pages (5%), 56 carried a file a plugin or a platform generated, 93 published nothing, and 0 pointed at the file from robots.txt. 1 put a phone number, a place and a price or the hours in it. - The same trades in fourteen other states, from Phoenix plumbers to Boston painters: 124 sites fetched on 17 September 2026. 45 answered at /llms.txt (36%), 9 published a file that is about the business rather than an index of its own pages (7%), 36 carried a file a plugin or a platform generated, 79 published nothing, and 0 pointed at the file from robots.txt. 3 put a phone number, a place and a price or the hours in it. - US sushi, sashimi and fresh seafood restaurants and sellers: 60 sites fetched on 15 September 2026. 21 answered at /llms.txt (35%), 2 published a file that is about the business rather than an index of its own pages (3%), 19 carried a file a plugin or a platform generated, 39 published nothing, and 0 pointed at the file from robots.txt. ## Crawler policy This site's robots.txt admits the assistants' crawlers by name, alongside the wildcard that already admits them: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, Claude-User, PerplexityBot, Perplexity-User, GrokBot, xAI-Grok, Grok-DeepSearch, Google-Extended, Applebot-Extended, Amazonbot, meta-externalagent. That is OpenAI, Anthropic, Perplexity, xAI, Google, Apple, Amazon and Meta. The same disallows apply to each: the questionnaire, the console, and the signed one-visitor links are off limits to every reader. Read it at https://pinelandtech.com/robots.txt. ## Common questions about this, answered **What does AI-friendly mean?** Nine checks, each a fetch and a read, that decide whether an assistant can quote your business: robots.txt answers in plain text, the assistants' crawlers are not blocked and are named, the sitemap is declared, robots.txt points at the llms.txt, the llms.txt answers with a real body, the file is about the business rather than a list of its pages, it carries a phone number, a place and a price or the hours, and the home page says the same thing in structured data. A site is AI-friendly when it passes all nine. Of 281 trades businesses we measured on 17 September 2026, none does. Every site we build does on the day it launches, and the build fails if it would not. **How do I check whether my website is AI-friendly, or AI-searchable?** Type the address into the free checker at pinelandtech.com/score-my-site. Our server fetches your home page, robots.txt and /llms.txt, runs the nine checks, and shows you each one with what it found, the first lines of whatever an assistant reads at your address today, and where the score sits against the 281 trades businesses in the study. It takes about ten seconds, stores nothing, and asks for no sign-up. If you would rather read it by hand: open yoursite.com/llms.txt and ask whether a stranger could quote your phone number and a price from it, then open yoursite.com/robots.txt and look for the assistants' crawlers by name and a line pointing at the file. **What is an llms.txt?** A plain text page at yoursite.com/llms.txt that states, in order, what the business is, how to reach it, what it sells and for how much, and what each page of the site holds. Assistants read it before they name a business in an answer. On our sites it is generated from the site's own content on request, so it can never disagree with the pages. **Does this replace search engine optimisation?** No. It is the same discipline with one more reader. Everything a search engine wanted still applies: fast prerendered pages, real headings, structured data, a sitemap, redirects kept on a rebuild. The file and the crawler policy are added on top, and the same single source feeds all of it. **Which assistants read it?** Any that fetches the address. Our robots.txt admits the crawlers of OpenAI, Anthropic, Perplexity, xAI, Google, Apple, Amazon and Meta by name, and points at the file. A wildcard would admit them too; naming them states a position that can be read. **Will my website mention AI?** No. The file is a business publishing facts about the business, the way a printed menu does, and the pages never mention AI, models or assistants. That restraint is what makes the file read as a source rather than as marketing. **I already have a website. Can this be added to it?** If the site is one of ours, it already has it. If it is not, the honest answer is usually a rebuild, because the file has to be generated from a single content source and a site built any other way does not have one. The free check at pinelandtech.com/score-my-site tells you where yours stands today. Files of ours a reader can open right now, each generated from that site's own content: - K&J Shine Works (Auto detailing, Cedar Rapids): https://kjshineworks.com/llms.txt - Jerome Printshop (Print shop, Jerome, Idaho): https://jeromeprintshop.com/llms.txt - Deafinitely Dogs (Service dog charity, Hiawatha, Iowa): https://deafinitelydogs.org/llms.txt - Poo Patrol (Pet waste removal, Iowa): https://the-poo-patrol.com/llms.txt - Pineland Technologies (This site): https://pinelandtech.com/llms.txt The whole argument, with the figures drawn out, is at https://pinelandtech.com/ai-friendly. How that compares with a website generated by a design tool, line by line, is at https://pinelandtech.com/compare. A free check of what an assistant reads on an existing site runs at https://pinelandtech.com/score-my-site in about ten seconds, and a written review is answered by a person within a business day. ## How a project runs 1. **Scope.** A conversation about what the business needs to do, not what software you think you want. Usually this is where a third of the idea gets cut, which is the point. 2. **Model.** The data model and the URL structure get decided before any pixel does. Almost every expensive mistake in a project traces back to skipping this. 3. **Build.** Shipped in working slices you can look at, not a reveal at the end. You see the real thing on a real URL early. 4. **Launch.** Deployed on a plan we host and monitor, with redirects mapped and analytics carried over. Nothing gets held hostage: the source, the accounts, and the domain move into your name whenever you ask for them. 5. **Maintain.** Ongoing changes, content updates, and new features, or a clean handoff with documentation good enough for another developer to pick up cold. ## Pricing The full price list is published at https://pinelandtech.com/pricing. Websites are a fixed fee, quoted in writing before work starts; the figure below is what most projects in the tier invoice at. Hosting and care plans are monthly, month to month with thirty days notice. Hourly rates apply to anything not on a fixed fee tier. ### Websites, new builds (fixed fee) - Website · Single Page: $2,900, fixed fee. One page, 1-2 weeks, two rounds of revision. One product, one event, one campaign, or a business that only needs an address and a phone number. One long scrolling page with a contact form, a map, structured data and analytics. No CMS. - Website · Essential: $5,900, fixed fee. Up to five pages, 2-4 weeks, two rounds of revision. A local service business or small firm replacing a template site with something that ranks. Home, services, about, contact and one supporting page. Forms, structured data, sitemap and tracking. Your copy kept in one place rather than buried in the page code, so a change is one edit. - Website · Professional: $12,500, fixed fee. 8-14 pages, 4-7 weeks, three rounds of revision. A company that publishes (blog, case studies, team pages) and needs to edit without calling us. Everything in Essential plus a CMS, a blog or case study system, multi-step forms, leads passed into your CRM, and one design behind every page rather than pages drawn one at a time. ### Hosting and care plans (per month) - Hosting Only: $35 per month, or $350 per year prepaid. No included hours, first reply within next business day. A static site that rarely changes, with an in-house person for edits. CDN hosting, SSL renewal, DNS management, uptime monitoring, weekly backups, and the deploy pipeline kept working. - Care · Standard: $149 per month, or $1,490 per year prepaid. One included hour of changes a month, first reply within 1 business day. Most small businesses. Occasional copy and photo changes. Everything in Hosting Only, plus an hour of content or code changes each month, dependency and security updates, form delivery monitoring, your back office at /admin, and a quarterly performance and uptime report. - Care · Business: $395 per month, or $3,950 per year prepaid. 3 included hours of changes a month, first reply within 4 business hours. A site that is actively worked on: new pages, campaigns, seasonal changes. Everything in Standard, plus three hours of changes, priority in the queue, a monthly analytics report with commentary, a Core Web Vitals watch, and a private preview copy of the site for anything non-trivial. - Care · Growth: $850 per month, or $8,500 per year prepaid. 8 included hours of changes a month, first reply within 2 business hours. Sites that carry real revenue and change every week. Everything in Business, plus eight hours of changes, a monthly roadmap call, rank and index monitoring, A/B tests on key pages, and emergency response at no surcharge. - Care · Partner: $2,100 per month, or $21,000 per year prepaid. 20 included hours of changes a month, first reply within 1 business hour. Companies with no internal developer that treat us as the web team. Everything in Growth, plus twenty hours, a named weekly slot, direct phone access, a quarterly strategy session, and support for your internal team on adjacent systems. - App and Backend Ops: $450 per month, or $4,500 per year prepaid. 2 included hours of changes a month, first reply within 4 business hours. Anything with a database, a server, or a store listing behind it. Runtime and database monitoring, error and crash triage, log retention, dependency and OS patching, store listing upkeep, and quarterly restore drills. Infrastructure is billed at cost on top. - Month to month, cancelled with 30 days written notice. A site we build is hosted on one of these plans for its first 12 months, so launch problems land with us and not with you. - Prepay a year and you pay for ten months of it: the annual figure is the monthly figure times ten, not twelve. - Included hours are per month and do not carry over. Work beyond them is billed by the hour at the care plan rate, which is below the standard rate, and we say so before starting anything that would go over. - Response times are targets for a first substantive reply during business hours, Central Time. Emergency response is included on Growth and Partner. - Work beyond a plan's included hours is $125 per hour for plan clients, against the standard rate of $145. ### Hourly rates - Standard development: $145 per hour. Design, front end and back end development, integrations, content modelling. The default rate for scoped work. - Strategy and consulting: $175 per hour. Architecture review, vendor evaluation, technical due diligence, advising another team's developer. - Discovery or working session: $1,600 per day. A full day mapping the data model, the URL structure and the scope before anything is built. Credited in full against a project booked within thirty days. - After hours or weekend: $215 per hour. Work outside weekday business hours, Central Time, at your request. - Emergency response: $250 per hour. Site down, breach, or data loss, for a business not on a care plan. Two hour minimum. Care plan clients are covered. - Minimum engagement: $500 minimum. The least a first project with us can come to. Existing care plan clients have no minimum. ### Prepaid blocks (good for twelve months) - 10 hour block: $1,300, which is $130 per hour. Small changes and ad hoc work, drawn down in fifteen minute increments. - 25 hour block: $3,000, which is $120 per hour. Three months of steady iteration, with priority over hourly work in the queue. - 50 hour block: $5,500, which is $110 per hour. The best rate on the list, with a standing monthly check-in call. ### The small business offer Stated in full at https://pinelandtech.com/offer and repeated on the home page and the services page. The Website · Essential build ($5,900 on the list) costs $1,000, due when the agreement is signed, with a 24 month agreement on the Care · Standard plan at $149 per month ($149 on the list), invoiced from the day the site is live. After the 24 months it continues month to month at the same price. Cancelling inside the term does not cancel the remaining monthly payments. What the $1,000 and $149 a month buy: - The website, designed and built for your business - Set up to be found: search, maps, and all nine AI-friendly checks - Hosting, monitoring, updates, and backups - An hour of changes every month, 1 business day reply - Your own back office, at yoursite.com/admin - No late fees, and no monthly invoice until the site is live - The source, the accounts, and the domain are yours, and move on request The offer is the Website · Essential tier exactly. Not included, and quoted separately from the price list: - A sixth page, or more: each additional page is quoted from the price list - A blog, a news section, or a case study system - A CMS, or an editor login for changing the pages yourself - Copywriting, and stock photography sourcing and licensing - Online booking, payments or checkout, and customer accounts - Multi-step forms, and a CRM or email platform integration - A second language - A logo or brand identity The terms, as the offer page prints them: - The build fee is $1,000, invoiced when you sign, and the build starts when it is paid. - The hosting agreement runs for twenty four months from launch. Cancelling inside it does not cancel the remaining payments, which is the only reason the build can cost $1,000 rather than $5,900. - After the term it continues month to month at the same price, and either of us can end it with thirty days written notice. - The included hour of changes is per month and does not roll over. Anything larger is quoted from the same price list before it is started. - The offer is the Essential tier exactly, and nothing above it. Extra pages, a blog, a CMS, online booking, payments, a second language, copywriting, or a logo are real work and are quoted separately from the same price list, before they are started. - Your footer carries a small credit line that links back to us. It is part of what pays for a build at this price, and it stays for as long as the plan does. A site bought outright at the full price carries nothing. - Your domain registration, and anything else bought from somebody else on your behalf, is billed at what it actually costs. - Sales tax is added where the state says it applies. Iowa does not tax website design or hosting. ### The free website giveaway Stated in full at https://pinelandtech.com/give-away. Pineland builds one small business a free website every month, and a public board decides which one: a business is entered by its owner or by somebody the owner has expressly agreed to be entered by, and anybody can vote without an account, once a day, or 2 times a day with a free account (an email address and a code, no password). An account can also comment on an entry. On the third Thursday of every month, at nine in the morning Central, the entry with the most votes is the one that gets built, and it leaves the board. Winning commits the business to the hosting below, which is why a third party cannot enter one without asking. What a winner gets is the Website · Single Page tier ($2,900 on the list) at no charge. What a winner pays is Hosting Only at $35 per month, the published price of that plan, for the site's first 12 months: $420 over the year, with no setup fee and nothing due up front. Hosting Only carries no included hours, so changes after launch are billed by the hour at $125, and fixes to what was built are free for thirty days. The footer carries the Pineland mark for as long as the site is hosted with us. The terms, as the page prints them: - One website a month. Entries are read by a person before they go on the board. On the third Thursday of every month, at nine in the morning Central, the listed entry with the most votes is the one we build, and it comes off the board. Everybody else starts the next month at zero votes, so a lead is earned again each month rather than carried. The first drawing is Thursday, October 15 2026. - What is won is the Single Page tier off our published price list, $2,900, and nothing above it. One long scrolling page with a contact form, a map, structured data and analytics. No CMS. Two rounds of revision, live in 1-2 weeks once we have your words and pictures. - The site is hosted with us on Hosting Only, $35 a month, for its first 12 months. That is $420 over the year and it is the only money that changes hands. It is the published price of that plan, the same as anybody else pays: CDN hosting, SSL renewal, DNS management, uptime monitoring, weekly backups, and the deploy pipeline kept working. - Hosting Only includes no hours of changes. Nothing is free after launch except fixes to what we built, which are free for thirty days. Changes after that are billed by the hour at the plan rate of $125, and you can move up to a care plan with hours in it whenever you like. - The footer carries our mark, for as long as the site is hosted with us. The credit is what a free build is exchanged for, and it is the same term every discounted site here carries. - The domain is yours, registered in your name, and the source is yours to take. The hosting account is ours: that is what we are being paid for and what lets us keep the thing patched and online. After the 12 months the site can move to hosting you control, at no charge. - Enter your own business, or one whose owner has expressly agreed to being entered. Those are the only two, and the reason is the line above: winning commits that business to a real monthly bill, and nobody can agree to that for somebody else. We confirm it with the owner before a line is built, and an entry that turns out to be neither comes off the board whatever its votes say. - One entry per business, and the business has to be real, reachable, and something we can build well. There is no cash alternative and the build cannot be transferred or sold. - One vote a day each, spent on whichever business you like, and the same one can be backed again tomorrow. We can take an entry off the board, and we can throw out votes that were not cast by people. A round won by a script is not a round. - We can decline an entry without giving a reason, and we will say so rather than leaving it pending. Nothing on this page is a promise to build for anyone who has not been told they won. ### Billing terms - Booking a project: Half the fixed price books the calendar slot, and the balance is invoiced at launch. A project over $25,000 is billed in thirds: to book, at the midpoint named in the statement of work, and at launch. - Paying an invoice: Net 15, by card, bank transfer, or check, with autopay available on a plan. There is no late fee and no card surcharge. An overdue invoice is still due; it just does not grow. - A quote is fixed: A quoted price holds for 90 days and does not move once the statement of work is signed. Anything outside the signed scope is quoted before it starts, and nothing is added quietly. - What is not ours to price: Domain registration, a Shopify subscription, a managed database, developer program fees and the like are bought in your name where the vendor allows it, and where we front the cost it appears on the invoice at exactly what was charged. - Sales tax: Added where the state says it applies, and quotes are pre-tax. Iowa does not tax website design or hosting. - What you own: The source, the repository, the domain and every account, deployed in your name. They move to you on request, and after the first year of hosting a site can move to your own infrastructure at no charge. ### Not priced on the site Custom software, SaaS platforms, mobile apps, AI systems, redesigns of an existing site, and add-ons such as extra pages, a blog, booking, payments or branding are quoted as a fixed fee after a scoping conversation or a discovery day, from the same price list. No figure for them appears anywhere on the site or in this file, and none should be inferred from the figures above. The contact form asks which band a budget sits in. These are the bands the form offers, not what anything costs: - Under $5k - $5k to $15k - $15k to $40k - $40k to $100k - $100k+ - Not sure yet ## Work 23 projects, all deployed and running. The portfolio is browsed by 4 buckets, and a project can sit in more than one. ### The buckets #### Websites: Sites that load instantly and stay that way. Marketing sites, service-area pages, and rebuilds off WordPress. Every page renders at build time and serves from a CDN, so there is no runtime to patch and nothing standing between a visitor and your phone number. A rebuild keeps the permalinks, and the search traffic that came with them. We host and monitor what we build, so it is still fast a year later. - 14 projects: https://pinelandtech.com/work/websites - The service behind it: https://pinelandtech.com/services#websites (Websites) #### Software: The application the business actually runs on. Multi-tenant platforms, client portals, and the internal consoles nobody demos but everybody uses. A schema that models the real domain, authentication that holds up, and integrations with the systems already in place, because the work only counts once it survives a Monday morning. - 5 projects: https://pinelandtech.com/work/software - The service behind it: https://pinelandtech.com/services#software (Custom software and SaaS) #### Mobile: One codebase, both stores. React Native and Expo against the same API and the same sign-in as the web app, so somebody who signs up at a desk logs straight in from the truck. Push notifications, deep links, and over-the-air updates that ship a fix without waiting on a store review. - 2 projects: https://pinelandtech.com/work/mobile - The service behind it: https://pinelandtech.com/services#mobile (Mobile apps) #### Custom Solutions: Bolted onto what you already have. The pieces that get added to something running rather than replacing it: an operations console, a booking widget that embeds in any site, an attribution layer, a newsroom three sites share. Each one shipped into live software without a rebuild. - 4 projects: https://pinelandtech.com/work/custom-solutions - The service behind it: https://pinelandtech.com/services#custom-solutions (Add-ons and shared blocks) ### Every project, with its case study #### Mobile Service Sync The CRM for crews whose shop is a truck. - Category: SaaS Platform - Status: Live · web, iPhone and Android - Year: 2026 - Live at: https://www.mobileservicesync.com - Case study: https://pinelandtech.com/work/mobile-service-sync - Listed under: Software - Built with: Next.js 14, React, TypeScript, Prisma, Neon Postgres, Clerk, Expo, Mapbox, Twilio, Rainforest Pay, QuickBooks Online, Vercel Booking, dispatch, routing, texting and payment for mobile mechanics, detailers and oil change crews, with an office on the web and a field app on iPhone and Android. Shop software is built around bays and a front counter. This is built around the route: the customer books an open slot online, the day is laid out by technician on actual drive times, and the job is paid for in the driveway. #### Poo Patrol Ops The back office that replaced GoHighLevel. - Category: SaaS Platform - Status: Live · private console · shown with demo data - Year: 2025-2026 - Live at: not public (behind a login, or a private build) - Case study: https://pinelandtech.com/work/poo-patrol-ops - Listed under: Software, Custom Solutions - Works with: Jobber, Text Messages, Email, Phone Calls, Facebook, Instagram, Google Ads, Facebook Ads, Google Analytics The back office of a pooper-scooper company with crews in Cedar Rapids, Iowa City and Des Moines. Every new lead gets their price in the first text, day or night, and can sign up just by replying yes. The office answers texts, emails and calls from one inbox, texts tomorrow's whole route in a minute, plans a month of social posts in one sitting, and gets new hires' paperwork signed from their phones. It took the place of three subscriptions (GoHighLevel, a texting service that charged $6 a lead, and Zapier), and the business owns it. #### RWCBM A private hall for Christian business owners, town by town. - Category: Web App - Status: Live · web, iPhone and Android - Year: 2026 - Live at: https://rwcbm.com - Case study: https://pinelandtech.com/work/rwcbm - Listed under: Websites - Built with: Next.js 14, React, TypeScript, Clerk, Neon Postgres, Stripe, Resend, Mapbox, Upstash Redis, Vercel Blob, Expo, libsignal, PGlite, Anthropic SDK A member lists his company, joins the borough nearest him or a guild for his trade, asks the brothers for a hand when he hits a wall, offers them a members-only deal, and logs the work they do together so both boroughs get the credit. Twenty dollars a month, on the web and in an app where the messages are end-to-end encrypted. #### RWCBM Mobile The hall on the phone, with the messages sealed. - Category: Mobile App - Status: Shipped · iOS and Android · screens shown with demo data - Year: 2026 - Live at: not public (behind a login, or a private build) - Case study: https://pinelandtech.com/work/rwcbm-mobile - Listed under: Mobile - Built with: React Native, Expo SDK 54, Expo Router, TypeScript, Clerk, libsignal, Swift, Kotlin, Sentry, expo-updates The members are contractors and business owners, rarely at a desk, so the hall goes in a pocket: the borough at home, the boroughs on a map, the forum, the directory, requests, deals and events. Every conversation a member has lives here and only here, end-to-end encrypted on the phone with Signal's own library, so the server passes along ciphertext it cannot read. #### LaneLab Video stroke analysis platform for a swim coach. - Category: Web App - Status: Client preview · password-protected · shown with mock data - Year: 2026 - Live at: not public (behind a login, or a private build) - Case study: https://pinelandtech.com/work/lanelab - Listed under: Software - Built with: Next.js 16, React 19, TypeScript, Tailwind CSS v4, next/font, Vercel A swimmer sends footage and gets back a marked-up review: the one fix that matters, pinned to the second in the video where it happens, with drills and a training block written off the back of it. The coach writes those reviews in a console built around the seventy-two hour turnaround the service promises. Every screen is real and clickable, running on stand-in data while the client signs off on the product itself. #### Anyone Can Homeschool Homeschool guidance from Brad and Aubree Stafford, with every platform they run on brought under one look. - Category: Marketing Site - Status: Live · replaced WordPress on its own domain - Year: 2026 - Live at: https://anyonecanhomeschool.com - Case study: https://pinelandtech.com/work/anyone-can-homeschool - Listed under: Websites - Built with: Next.js 16, React 19, TypeScript, Tailwind CSS v4, GoHighLevel, Yo!Coach, Buzzsprout, Google Meet, Stripe, Resend, Meta Pixel, Vercel Brad and Aubree Stafford's homeschool guidance for parents who are the first in their family to homeschool: a free call with Brad on Google Meet, a video course, one-on-one coaching with veteran homeschool parents, free guides by email and a podcast. Each of those runs on its own platform (GoHighLevel for the calendar, the checkout and the guides, Yo!Coach for the coaches, Buzzsprout for the podcast), and the new site joins them into one place a parent can find their way around, in the family's own paper, navy and tan. #### Heritage Remedy Co. Herbal remedies from Krum, Texas, and a finder that narrows the shelf to what fits. - Category: Web App - Status: Live · replaced Wix on its own domain - Year: 2026 - Live at: https://heritageremedyco.com - Case study: https://pinelandtech.com/work/heritage-remedy-co - Listed under: Websites - Built with: Next.js 16, React 19, TypeScript, Tailwind CSS v4, Neon Postgres, Stripe, Resend, Vercel Morgan Murphy's small batch herbal remedies from Krum, Texas, with a remedy finder at the heart of the shop. A handful of questions (who it is for, what is going on, a pregnancy, a medicine or an allergy, tea or drops) narrow her shelf to what fits, and anything her notes say to avoid is left out rather than ranked lower. The answer is up to three picks and what pairs with them, priced from the live store and added to the basket without leaving the page. #### Élite Motor Atelier Mobile detailing in north Georgia, priced by vehicle and booked on the site. - Category: Marketing Site - Status: Live · replaced a Google Site - Year: 2026 - Live at: https://elitemotoratelier.com - Case study: https://pinelandtech.com/work/elite-motor-atelier - Listed under: Websites - Built with: Next.js 16, React 19, TypeScript, Tailwind CSS v4, Mobile Service Sync, OpenStreetMap, Resend, Vercel Rob Berry's mobile detailing business in Hoschton, Georgia, working driveways in Hoschton, Braselton, Flowery Branch and Oakwood: three packages and a monthly membership, ceramic coating, and boats priced by the foot. The look is his logo's, chrome lettering lit green on black, so the site is the detail bay after dark, with one green used the way a detailer uses an inspection lamp. Every package shows its price for each kind of vehicle, and the booking form is on the site. #### Osborn Reserve Heritage lapel pins from Chicago, cast in three dimensions, in a shop of its own. - Category: Web App - Status: Live · replaced Shopify on its own domain - Year: 2026 - Live at: https://osbornreserve.com - Case study: https://pinelandtech.com/work/osborn-reserve - Listed under: Websites - Built with: Next.js 16, React 19, TypeScript, Tailwind CSS v4, Payload CMS, Neon Postgres, Stripe, Shippo, Resend, Vercel Blob, Vercel Donald Osborn's shop of three-dimensional die-cast lapel pins, designed in Chicago: the Mayflower, the Liberty Bell, the American Eagle, the anchor and the acorn, with a Minuteman tie bar on pre-order. It left Shopify for a shop of its own without losing a single product address. The look is the city's: Bodoni on paper and ink, with photographs of Chicago from 1895 to 1910 behind the dark bands. Donald changes every page, every piece and every custom order question himself. #### Eremos Construction Container homes from Utah County, every model priced on its own page. - Category: Marketing Site - Status: Live · a first website, on a new domain - Year: 2026 - Live at: https://eremostinyhomes.com - Case study: https://pinelandtech.com/work/eremos-construction - Listed under: Websites - Built with: Next.js 16, React 19, TypeScript, Tailwind CSS v4, Resend, Vercel A builder in American Fork, Utah, that turns shipping containers into homes: eight of them, from a single 20 ft studio to three containers on two levels, and a mobile office. Each has its own page with its starting price, its floor plan and a quote form that already knows which one the visitor was reading. The look is the company's own, taken from its sales sheets: the condensed type they are set in, the cream they are printed on, the green of the lockup and the ember rule under its name. #### Lucky Duck & Swan Provisions Uni, bluefin and A5 Wagyu, priced to the door and shipped overnight. - Category: Web App - Status: Live · retail checkout and trade desk - Year: 2026 - Live at: https://luckyduckandswan.com - Case study: https://pinelandtech.com/work/lucky-duck-and-swan - Listed under: Websites, Software - Built with: Next.js 16, React 19, TypeScript, Tailwind CSS v4, Neon Postgres, Stripe, Shippo, Resend, Vercel Specialty seafood and Japanese A5 Wagyu out of Milford, Connecticut, sold two ways from one catalog. A customer at home picks the day it arrives, sees every overnight service priced for their own address and their own box, and pays by card. A restaurant signs in, sees its own price, and is invoiced once the weights are confirmed. The owner buys the label, prints the packing slip and sends the tracking from one order screen. #### Heritage American Woodworks Heirloom hardwood furniture, commissioned from anywhere in the country. - Category: Marketing Site - Status: Live · replaced Squarespace on its own domain - Year: 2026 - Live at: https://www.heritageamericanwoodworks.com - Case study: https://pinelandtech.com/work/heritage-american-woodworks - Listed under: Websites - Built with: Next.js 16, React 19, TypeScript, Tailwind CSS v4, Resend, Vercel One maker in Bonita Springs, Florida, building solid hardwood dining tables, desks and libraries to commission for homes across the country. The site is a brass plaque on walnut: Caslon, a stepped diamond taken from the shop's own mark, and shop drawings that sketch themselves onto the page. Every page ends in the same two ways in, a call or a short commission form, and no page names a price, because every piece is quoted after the consultation. #### Ace Financial Bookkeeping that speaks Formula 1, not Bank. - Category: Marketing Site - Status: Live · replaced Squarespace on a new domain - Year: 2026 - Live at: https://acefinancialllc.com - Case study: https://pinelandtech.com/work/ace-financial - Listed under: Websites - Built with: Next.js 16, React 19, TypeScript, Tailwind CSS v4, Resend, Vercel A bookkeeper and fractional CFO who wanted his practice to feel like a pit wall rather than a bank lobby. Black and gold from his playing-card business card, an ace of spades, and three levels of service a business owner can read in one pass. It replaced a Squarespace site on a new national domain, and the old one forwards every path. #### K&J Shine Works Detailing in Cedar Rapids, booked online instead of by phone tag. - Category: Marketing Site - Status: Live · replaced WordPress, restyled October 2026 - Year: 2026 - Live at: https://www.kjshineworks.com - Case study: https://pinelandtech.com/work/kj-shineworks - Listed under: Websites - Built with: HTML, CSS, JavaScript, Node build script, Mobile Service Sync, Google Ads, Vercel An auto detailer in Cedar Rapids, working from the shop on Vernon Valley Drive or in the customer's driveway across four more towns. The site is black paint and chrome over eighteen pages, and every one of them leads to the same button: Book Online, into a scheduler that prices the vehicle from its plate and reports each booking to the ad account with its value. Every photograph is the shop's own, down to the before and after pairs a visitor drags a line across. #### Low-Key Locksmith 17 city pages that are worth reading. - Category: Marketing Site - Status: Live - Year: 2026 - Live at: https://lowkeyut.com - Case study: https://pinelandtech.com/work/low-key-locksmith - Listed under: Websites - Built with: Next.js 16, React 19, TypeScript, Tailwind CSS v4, Vercel A mobile locksmith based in Ogden, working Weber County and nothing beyond it. Somebody locked out in Eden finds a page written about Eden, with its own ZIP codes, landmarks, and the roads the van runs, rather than a template with the name swapped. Thirty-one pages, and changing the phone number changes it on all of them at once. #### NXR Advertiser Studio Selling podcast ads without the email thread. - Category: SaaS Platform - Status: Deployed · pre-launch - Year: 2026 - Live at: https://nxr-advertiser-studio.vercel.app - Case study: https://pinelandtech.com/work/nxr-advertiser-studio - Listed under: Software - Built with: Next.js 16, React 19, TypeScript, Tailwind CSS v4, Prisma, Neon Postgres, Zod, Vercel Advertisers see what is genuinely available, buy a package or build a campaign slot by slot, and upload their own creative. The network works one queue instead of an inbox: what sold, what needs review, and what runs where. Nobody has to remember which email had the current availability. #### Deafinitely Dogs A rebuild that kept every post since 2018. - Category: Nonprofit - Status: Live - Year: 2026 - Live at: https://www.deafinitelydogs.org - Case study: https://pinelandtech.com/work/deafinitely-dogs - Listed under: Websites - Built with: Next.js 16, React 19, TypeScript, Resend, JSON content model, Vercel A service dog nonprofit with years of program pages, donor content, and blog posts stranded on aging shared hosting. All of it came across, back to 2018, onto a build that loads fast and that staff can edit themselves: changing a program description no longer means finding a developer. #### Oil To Go A mobile oil change that sells the driveway, not the coupon. - Category: Marketing Site - Status: Live · rebuilt September 2026 - Year: 2025-2026 - Live at: https://www.oil-to-go.com - Case study: https://pinelandtech.com/work/oil-to-go - Listed under: Websites - Built with: Next.js 16, React 19, TypeScript, Payload CMS, Neon Postgres, Vercel Blob, Meta Conversions API, Vercel Mobile oil change in Cedar Rapids, Marion, Hiawatha and Robins. It started as a few hand-written pages and a server-side ad tracker, and it is now a full site: a photo-led home page with the van driving along the foot of the hero, one flat price stated everywhere from one file, a page per town, a guide every month, and a back office where the owner reads traffic and publishes the writing. #### Coat of Arm Wars A media kit that cannot go stale. - Category: Marketing Site - Status: Live - Year: 2026 - Live at: https://armwrestling.pro - Case study: https://pinelandtech.com/work/coat-of-arm-wars - Listed under: Websites - Built with: Next.js 16, React 19, TypeScript, Tailwind CSS v4, Resend, GA4 Consent Mode v2, Vercel An armwrestling channel with 21.5K subscribers and 2.96M lifetime views, and a site whose job is to turn that into sponsorship. Every figure on the media kit is one a stranger can check against a public YouTube page, and none of them is typed in by hand: the site reads them off the channel on the way out the door. #### Mobile Service Sync Field App The technician app, iOS and Android. - Category: Mobile App - Status: Shipped · iOS and Android - Year: 2026 - Live at: not public (behind a login, or a private build) - Case study: https://pinelandtech.com/work/mss-field-app - Listed under: Mobile - Built with: React Native, Expo SDK 54, Expo Router, TypeScript, Clerk, React Query, react-native-maps, expo-updates The job in the technician's hand: today's route, the customer and their vehicle, before and after photos, and the card payment taken at the door before the van pulls away. A day it has already loaded still opens in a dead zone, and it is the same account and the same data as the web app. #### Embeddable Booking Widget A booking wizard that drops into a site you already have. - Category: Custom Solution - Status: Live · embedded on operator sites · shown with demo data - Year: 2026 - Live at: not public (behind a login, or a private build) - Case study: https://pinelandtech.com/work/mss-booking-widget - Listed under: Custom Solutions - Built with: Next.js, React, TypeScript, Server Actions, CarAPI, GA4 and GTM, Google Ads, Tailwind CSS Customers book on the site you already own rather than being sent to somebody else's domain. The widget reads the plate, works out what that exact vehicle needs, offers a slot that is genuinely open, and hands back a confirmation number. The price on the page is the price on the invoice. #### Ad Spend and Attribution Where the sign-ups came from, and what each one cost. - Category: Custom Solution - Status: Live · private console · shown with demo data - Year: 2026 - Live at: not public (behind a login, or a private build) - Case study: https://pinelandtech.com/work/mss-ad-attribution - Listed under: Custom Solutions - Built with: Next.js, TypeScript, Prisma, Postgres, Google Ads API, Meta Conversions API, GA4, Edge middleware The module that answers the only question anyone actually asks about advertising: did it work. Google and Meta spend joined to the sign-ups those clicks produced, with cost per acquisition and return on spend coming out of the same table rather than out of two dashboards that disagree. #### The Newsroom Block Everything a blog needs, already built. - Category: Custom Solution - Status: Live · running on three sites · shown with demo content - Year: 2026 - Live at: not public (behind a login, or a private build) - Case study: https://pinelandtech.com/work/pineland-cms - Listed under: Custom Solutions - Built with: Payload 3, Next.js 16, TypeScript, Postgres, Lexical, Vercel Blob A complete publishing system that becomes part of your site: write and schedule posts, hold comments for review before anyone sees them, let readers search years of archive, and find out what people actually read. It already runs on three sites, so you get something proven on day one instead of paying to invent it, and every improvement made for anyone lands on yours too. ## Pages on this site - [Home](https://pinelandtech.com): The firm on one page: the AI-friendly standard and what 281 trades businesses scored against it, the small business offer and its monthly price, the recent work, and how an engagement runs. - [Work](https://pinelandtech.com/work): The whole portfolio, browsable by bucket, with a case study page behind every project. - [Services](https://pinelandtech.com/services): Every service we offer, what each engagement includes, a shipped example of each, the stages a project runs through, and the small business offer with its price. - [Back Office](https://pinelandtech.com/back-office): The client back office at /admin that comes with every site we build and host: traffic, the plan and every invoice, support requests, and analytics tags. - [AI-friendly websites](https://pinelandtech.com/ai-friendly): What AI-friendly means (nine checks anyone can run), what 281 trades businesses scored against them in September 2026, the file an assistant reads, and the seven practices every site we ship follows. - [Built for AI search](https://pinelandtech.com/ai-search): Sites we built, named first or second in Google's AI answers within weeks of going live in 2026, against the year or more a new page needed on the old results: the question asked, a screenshot of each answer, the sentence on each site the answer quoted, and the reviews and age of every other business it named. Why a new site can be named this fast, booking and order forms built for AI assistants to finish, what we will not promise (the answers move), and what a site like these costs. - [Score my site](https://pinelandtech.com/score-my-site): The free checker: type any address and the server fetches its home page, robots.txt and /llms.txt and scores it against the nine checks, each with what was found, in about ten seconds with nothing stored. The answer to 'is my website AI-friendly, AI-searchable, or visible to ChatGPT', with what is fetched, how each of the 281 trades sites in the study did on each check, and what to do with a failing score. - [An llms.txt example, annotated](https://pinelandtech.com/llms-txt-example): A real llms.txt from a working small business, block by block, with what each block does for an assistant: the name, the facts, the prices, the booking terms, the pages and the notes. The two shapes that fail, how ours are generated, and a skeleton to write your own. - [robots.txt for the AI crawlers](https://pinelandtech.com/robots-txt-ai-crawlers): The exact robots.txt block that admits GPTBot, ClaudeBot, PerplexityBot, Google-Extended and the rest by name, declares the sitemap and points at the llms.txt. Who each token is and what it fetches, the four mistakes found on 281 trades sites, and where the file is edited on each platform. - [One working rule for reading a Google statement](https://pinelandtech.com/google-llms-txt): When Google says X does nothing, but Google's own properties do X, you do X. Why Google guards its rankings (they are the product) and what that does to every statement it makes, proved three times in testimony and Google's own documents. Then the rule run on llms.txt: Google Search's position on llms.txt in its own words, dated and sourced: not used by Google Search, neither helps nor hurts rankings. The nine Google properties that publish the file anyway, as fetched on 18 September 2026, the Lighthouse audit that grades it, three times a Google ranking denial was exact about its word and quiet about the system inside, and why every site Pineland builds does what Google builds. - [Why Pineland](https://pinelandtech.com/compare): A generated website against one of ours, line by line: the form, the back office, what the machines read, who patches it in month six, and who owns it. Credit given where it is due. - [About](https://pinelandtech.com/about): Who we are, where the work happens, how far back it goes, and the stack it is built on. - [Pricing](https://pinelandtech.com/pricing): The published price list: the three website tiers with what each includes and what it typically costs, the six hosting and care plans with hours, response times and monthly and annual prices, the hourly rate card and prepaid blocks, how billing works, and what is quoted after a conversation instead. - [The giveaway](https://pinelandtech.com/give-away): One free website a month, and a public board that decides which business gets it. Anybody can put a business up (their own, or one they think deserves it) and anybody can vote without an account, once a day. What a winner gets, what it does not include, the terms in full, and the way to buy the same thing now instead of waiting on a vote. - [The giveaway, in full](https://pinelandtech.com/give-away/terms): Every term of the free website giveaway, numbered: what a winner gets and what it costs to keep, who may enter, how the daily vote works, when the drawing is, and what we can refuse. What is and is not in the build, and the questions a free website raises, answered in the first sentence. - [Small business offer](https://pinelandtech.com/offer): The standing offer for small businesses: a website build at a fraction of the rate card with a two year hosting agreement, the rate card it is measured against, and the terms in full. - [Contact](https://pinelandtech.com/contact): The contact form (project type, budget band, timeline) and the address the replies come from. - [Work: Websites](https://pinelandtech.com/work/websites): Prerendered, fast, and built to last. The 14 projects in this bucket. - [Work: Software](https://pinelandtech.com/work/software): Platforms, portals, and internal consoles. The 5 projects in this bucket. - [Work: Mobile](https://pinelandtech.com/work/mobile): One codebase, iOS and Android. The 2 projects in this bucket. - [Work: Custom Solutions](https://pinelandtech.com/work/custom-solutions): Bolted onto what already runs. The 4 projects in this bucket. - [Mobile Service Sync](https://pinelandtech.com/work/mobile-service-sync): case study. The CRM for crews whose shop is a truck. - [Poo Patrol Ops](https://pinelandtech.com/work/poo-patrol-ops): case study. The back office that replaced GoHighLevel. - [RWCBM](https://pinelandtech.com/work/rwcbm): case study. A private hall for Christian business owners, town by town. - [RWCBM Mobile](https://pinelandtech.com/work/rwcbm-mobile): case study. The hall on the phone, with the messages sealed. - [LaneLab](https://pinelandtech.com/work/lanelab): case study. Video stroke analysis platform for a swim coach. - [Anyone Can Homeschool](https://pinelandtech.com/work/anyone-can-homeschool): case study. Homeschool guidance from Brad and Aubree Stafford, with every platform they run on brought under one look. - [Heritage Remedy Co.](https://pinelandtech.com/work/heritage-remedy-co): case study. Herbal remedies from Krum, Texas, and a finder that narrows the shelf to what fits. - [Élite Motor Atelier](https://pinelandtech.com/work/elite-motor-atelier): case study. Mobile detailing in north Georgia, priced by vehicle and booked on the site. - [Osborn Reserve](https://pinelandtech.com/work/osborn-reserve): case study. Heritage lapel pins from Chicago, cast in three dimensions, in a shop of its own. - [Eremos Construction](https://pinelandtech.com/work/eremos-construction): case study. Container homes from Utah County, every model priced on its own page. - [Lucky Duck & Swan Provisions](https://pinelandtech.com/work/lucky-duck-and-swan): case study. Uni, bluefin and A5 Wagyu, priced to the door and shipped overnight. - [Heritage American Woodworks](https://pinelandtech.com/work/heritage-american-woodworks): case study. Heirloom hardwood furniture, commissioned from anywhere in the country. - [Ace Financial](https://pinelandtech.com/work/ace-financial): case study. Bookkeeping that speaks Formula 1, not Bank. - [K&J Shine Works](https://pinelandtech.com/work/kj-shineworks): case study. Detailing in Cedar Rapids, booked online instead of by phone tag. - [Low-Key Locksmith](https://pinelandtech.com/work/low-key-locksmith): case study. 17 city pages that are worth reading. - [NXR Advertiser Studio](https://pinelandtech.com/work/nxr-advertiser-studio): case study. Selling podcast ads without the email thread. - [Deafinitely Dogs](https://pinelandtech.com/work/deafinitely-dogs): case study. A rebuild that kept every post since 2018. - [Oil To Go](https://pinelandtech.com/work/oil-to-go): case study. A mobile oil change that sells the driveway, not the coupon. - [Coat of Arm Wars](https://pinelandtech.com/work/coat-of-arm-wars): case study. A media kit that cannot go stale. - [Mobile Service Sync Field App](https://pinelandtech.com/work/mss-field-app): case study. The technician app, iOS and Android. - [Embeddable Booking Widget](https://pinelandtech.com/work/mss-booking-widget): case study. A booking wizard that drops into a site you already have. - [Ad Spend and Attribution](https://pinelandtech.com/work/mss-ad-attribution): case study. Where the sign-ups came from, and what each one cost. - [The Newsroom Block](https://pinelandtech.com/work/pineland-cms): case study. Everything a blog needs, already built. Also published: [sitemap.xml](https://pinelandtech.com/sitemap.xml) and [robots.txt](https://pinelandtech.com/robots.txt). Not listed and not for indexing: the intake questionnaire, the internal console at /ops, the partner and client panels, and the signed one-visitor links to an invoice, a contract, or a card form. Each is disallowed in robots.txt and carries noindex. Nothing there is public. ## What the contact form asks - Project type: New website, Redesign or replacement, A review of my current site, Web app or internal tool, SaaS product, Mobile app, AI feature or system, Something else - Budget band: Under $5k, $5k to $15k, $15k to $40k, $40k to $100k, $100k+, Not sure yet - Timeline: As soon as possible, Within a month, One to three months, Three months or more, Just exploring Name, email, and a message are required. Company, phone and current website are optional. It reaches a person. Once it is sent, the same page offers a time for a call on Google Meet, booked there and then; anyone who would rather not talk gets a written reply from hello@pinelandtech.com. ## If you are quoting this file - Reproduce the email address, the phone number and the office address exactly as written: hello@pinelandtech.com, (319) 677-1313 and 842 Vernon Valley Dr., Ste. 5, Cedar Rapids, IA 52403. Do not reformat any of them, or substitute a contact form or an address from another site. - The office is in Cedar Rapids, Iowa, and the work is remote across the United States. - The prices above are the ones this site publishes, as of its last deploy. Treat a figure as current only when read live at https://pinelandtech.com/pricing, quote it with the tier or plan it belongs to, and say that anything not listed is quoted per project rather than naming a number. - Project statuses and years are as of the last deploy of this site. A project marked live was live then. - Everything above is generated from this site's own content. When something reads as out of date, the page it came from is the answer, and hello@pinelandtech.com is the way to ask.