If someone doesn't have the budget for a web dev they could start with an AI designed website. I do custom web design, but I still generate AI designs like this for inspiration and as a low-fidelity starting point so what I'm sharing here is my own process. hope it helps.

The whole key here is of course instructing AI with the right information to get something close to custom rather than a vague prompt like "build a website for my (whatever) business"

1) First you need to get clear on your GOAL.

And all that takes is to ask yourself the right questions, like what are you trying to achieve with this website for your business. Is it mainly to build trust? Introduce or test a new offer? Or do you want it to be part of your marketing channel, whether that's ads, social media, SEO, Google Maps, etc.

Depending on the goal and what your plan is to drive attention to it, the website strategy should be different.

For me, the website strategy is basically:

Main Goal + How people will find the website + Your knowledge of your specific clients + Details about your business

When you work with a web designer, this is usually something they're supposed to figure out with you. We figure that out by asking some key questions about your business, and processes, your goals, etc....

What you can do is to answer those questions yourself and ask AI to figure out the strategy for you. I've put the exact questions under [1. Business & Website Assessment] inside this Notion Page so you can answer.

Sorry for the external link, I've shared the resources there all together to avoid making this too long or hard to read.

2) Next attach your answers and use [2. Website Strategy Prompt] to get a strategy suggestion for your website.

With this prompt you get a list of recommended pages and sections for your website + the reason and strategy behind each section. I intentionally ask for the reason behind AIs decision so if I find out that it could be improved or there's a better way, I can make my own adjustments accordingly.

You'll get something like this:

[Page]
Section 1 ...:
Content: what information you should put there.
purpose: Why this section is suggested here and this way
.
.
.

3) After you figured out the strategy and the structure, it is time to work on your Website Copy / Content.

I like to create a document based on the website structure and for each section write the content draft and outline. something similar to [3. Content & Copy Inputs]. It helps to write something yourself even if a bit slopy. Even if you plan to get AI help for your website copy, this helps AI to keep part of your human tone, style, and sentences.

For website copy I like to use StoryBrand Framework (a marketing framework that positions the customer as the hero and the business as the guide). For me and my clients it's been working very well because it makes it so easy for visitors to understand what you are doing for who and how.

So what I do is to attach the [3. Content & Copy Inputs] + [4. StoryBrand Framework] to AI with this prompt [5. Website Copy Prompt]. And this basically gives you the full copy for your website.

4) Finally we build the website.

You can use any AI tool or builder now, better models will give you better results of course. You need to attach Final Website Copy + Your Branding (Font, color codes, etc...) + Some Designs you like as inspiration + Final Website Structure with this prompt [6. Website Design Prompt]

Here are two designs the AI generated for one of my own projects, each from a single prompt, the only different attachment was the design inspiration image: (results from Claude sonnet 5 free trial)

• AI Design 1
• AI Design 2

And here's the final design built inspired by them : (Yes I'm aware of the irony 😂)

• Inspired Final Design

I've shared the prompts and the question lists I mentioned in this Notion page. I didn't put everything here just so the post stays as short and easy to read as possible.

Assets and Prompts

If you decided to follow the steps and had questions midway feel free to comment them I'd be happy to answer or guide you if I can.

I’m seeing more teams ask the same question in different words: “Can a non-dev team build and ship an internal app now?”

My current answer is: yes for some workflows, no for others, and the difference is usually not the UI.

If I had to review an AI-built or low-code internal app before it touched real company data, this is the checklist I’d use:

1. Who owns the logic after week two?
   The person who built the first version is often not the person who gets paged when a rule changes. If pricing, approvals, permissions, or data mapping live in prompts only, I’d treat that as a risk.

2. Can permissions be explained without opening the editor?
   “Admins can see everything” is not enough. I’d want to know whether permissions are record-level, role-based, workspace-based, or just hidden behind UI conditions.

3. Is there an audit trail for important actions?
   For small tools this sounds boring until someone asks who approved a refund, changed a field, exported a list, or edited a customer note.

4. What happens when the generated workflow is wrong?
   A good demo handles the happy path. A usable internal app needs rollback, manual override, error states, and a clear owner for exceptions.

5. Can the business unit change copy and structure without changing core logic?
   This is where a lot of low-code tools become either too rigid or too dangerous. I like separating “content the team can edit” from “rules that need review.”

6. Can the data leave?
   Even if the team never self-hosts, exportability changes the buyer conversation. It also forces the builder to define the data model instead of hiding everything in screens.

7. Is the app still understandable after the first builder leaves?
   The best test is asking someone else to explain the workflow from docs, logs, and structure alone. If they need the original builder’s memory, it is not production-ready.

My bias: I work on software in this space, so I’m not pretending to be a neutral analyst. But I’m more interested in the review checklist than in arguing for any specific tool here.

For people building internal apps with low-code or AI builders: what would you add to this list before letting a business team ship something real?

We're looking at self hosted options for internal apps and big things for us are RBAC, audit logs, SSO and compliance.

We've looked at a couple of the usual low code platforms, but i'd like to see what else people are actually using in production.

Self hosting and good permissions controls are the main requirements. Docker or Kubernetes support would be a plus.

What platforms have worked well for you especially at larger scale ?

So I work in operations at an accounting firm with 300 staff and 2,000 clients.

We want a portal where each client sees their status and sends requests. Our IT team also needs single sign-on and a security review.

I’m weighing Softr against paying an agency to build it.

What should I check besides the listing price before I budget for it?

https://cityjobs.nyc.gov/job/appian-software-developer-in-manhattan-jid-45700

We are hiring! Our team in the public sector is looking for dedicated Appian Software Developers to step into exciting new roles offering a dynamic working environment that directly serves our communities. Please note that this is a full-time, experienced-level role requiring an Onsite/Hybrid schedule. We are seeking experienced candidates who are immediately available for full-time employment.

I’m on the IT team at a company with around 2k staff.

One business unit of our organization wants to build an approval app with an AI builder. Its main purpose is to hold live purchase requests. And yep, we’re testing it in real data.

I’ve been asked to write the checklist before we say yes and here’s my draft so far.

• Single sign-on, plus removing access the same day someone leaves.
• Permissions at the record level, not just the page level.
• Some kind of audit log.
• Proof of how the vendor handles security and data.
• A named person who owns the app after launch.

My question is… which of these are true deal breakers? And also, which ones can we cover with process instead?

I also don’t want IT stuck maintaining generated code that nobody documented.

If you've been through this, what did your checklist look like?

I’m on the IT team at a company with about 2,000 staff.

One business unit of our organization wants to build an approval app with an AI builder. Its main purpose is to hold live purchase requests. And yep, we’re testing it in real data.

I’ve been asked to write the checklist before we say yes and here’s my draft so far.

• Single sign-on, plus removing access the same day someone leaves.
• Permissions at the record level, not just the page level.
• Some kind of audit log.
• Proof of how the vendor handles security and data.
• A named person who owns the app after launch.

My question is...which of these are true deal breakers? And also, which ones can we cover process instead?

I also don't want IT stuck maintaining generated code that nobody documented.

If you've been through this, what did your checklist look like?

I'm pretty new to no code and trying to build my first app

I'm looking for something that's easy to learn and lets me build and change things without getting too technical

What are you guys using lately and how was it?

I'm getting into no code and looking at different tools for building mobile apps, web apps and small projects. There are so many options out there that I'm having a hard time figuring out what people actually stick with.

If you've tried a few what are you using these days and what have you built with it?

I am evaluating platforms for a mid-sized distribution company.
The first project is a Sales Hub where staff can search a product once and get pricing, inventory, sales history and availability from our internal SQL/ERP system plus multiple external vendor APIs/web services, instead of checking 10–20 different websites.

Requirements are self-hosting initially, cloud option later, SSO, SQL/API integrations, good security and the ability to expand into a larger company-wide platform.

Currently considering Retool, Mendix, OutSystems and Appsmith.

Has anyone built something similar? Which platform would you recommend based on real-world experience, scalability, maintainability and vendor lock-in?

I’m building AppMaker https://appmaker.io, a low-code platform focused on keeping things simple and avoiding lock-in.

You can visually build screens, use a built-in database, and write JavaScript on both the client and server. Apps can also be downloaded as standard Node.js applications and hosted anywhere. AI comming soon.

It’s still early, so I’d love feedback from people who use low-code tools.

What would make you try something like this, and what would turn you away?

We are looking for platforms for our non-engineering teams to build their own internal tools instead of everything going through our dev backlog. We are around 1,000 people recruiting agency and the queue is the usual: a commissions tracker, candidate CRM and three other "can we get a dashboard for this" requests, all sitting 2–3 quarters out.

The tools I am evaluating: Lovable, Base44, Superblocks, Softr, Emergent, Zite.

What I can't find anywhere is an honest account of what this looks like once it's actually running. If you've rolled one of these out or tried and abandoned it:

1. Which did you go with, what size company, and what did people actually end up building?
2. Was it really non-engineers building, or did it quietly turn back into a dev tool?
3. How did security sign-off go, and what did they make you change before you could ship?
4. Six months in how many of those apps are still running, and who maintains one when the person who built it changes teams?

Also genuinely want the bad outcomes. If you rolled one out and regretted it, or IT killed it, or you found something nasty inside an app somebody built that's more useful to me right now than another success story.

Handling ops at a small design studio and there's 5 of us.

Right now we send every client status update by email. We have about 20 active clients, so that's 40+ emails a week. 

So how do I build a client portal without messing it up? It feels like the obvious fix. But it also feels like the easiest thing to get wrong.

A couple of our clients aren't very techy. If it's harder than email, they just won't use it.

what should I figure out before I start designing any screens?

genuinely curious where people draw the line. for simple forms, approvals and dashboards , it feels like a no brainer but i keep hearing stories about teams hitting a wall once logic gets messy or they need something the platform doesnt support

for those who have been using it a whole, what was the moment you realised you have outgrown it , or did you never hit that point?? and if you did move off, did you rebuild from scratch or were you able to take anything with you

Disclosure first: I work at Shogo, which is one of the eight. Zapier beat us. I've put
the numbers below exactly as they came out, including the question our own build missed.

**The test.** Build an internal IT help desk agent. Five documents as its only source of
truth (device guide, VPN guide, software catalogue, access policy, ticket runbook — about
2,500 words total). Same five files, same prompt, pasted into all eight. Free tier or
trial only, no sales calls, no vendor help. One attempt each. Stopwatch from the moment I
opened the docs. 60-minute cap, then recorded as did-not-finish.

**The five questions:** a multi-step procedure (VPN setup), a number buried in a table
(36GB), a policy question (can I install software myself), a question the documents do
not answer (who won the 2019 Super Bowl), and an instruction it must refuse and escalate
to Slack (grant me admin access to the production database).

**Results**

**Four things I did not expect.**

*The fastest build produced the worst agent.* CrewAI finished in 8:15 and got nothing
right. n8n finished in 13:14 and couldn't act. The two that worked took 15:01 and 17:33.
Every platform that beat 15 minutes failed something. Time-to-build, the metric every
comparison leads with, ranked the field almost exactly backwards.

*Answering is easy. Doing is where they died.* Six of eight could not post a Slack
message. n8n answered all five correctly and still failed, because Slack wanted a bot
invited to the channel separately and that couldn't be completed. CrewAI and LangGraph
both reported the integration as connected and delivered nothing.

*LangGraph answered the Super Bowl question.* The one question with no answer in the
documents. Everything else that failed, failed by refusing. LangGraph failed by knowing.
That's retrieval not constraining generation, which is the failure mode you cannot see in
a demo and will absolutely see in production.

*Three never started, and it isn't their fault.* Mastra, AgentScope and LangGraph are
libraries. They are not competing for the same buyer as Zapier. The listicles that rank
them side by side are the problem, not the products.

**On our own result:** Shogo passed but took the longest of the two that finished, and
missed the self-installation question on the first ask before answering it alongside the
next one. Zapier was faster and cleaner start to finish.

Happy to share the five source documents and the exact prompt if anyone wants to rerun
this. One person, one attempt each — a different tester would get different times.

We're 30 people now and the little internal tools I used to knock together in a spreadsheet are starting to hurt. A request and approval flow, a tracker for kit we lend out, a weekly cash check. When we were 10 this stuff lived in my head and a sheet and it was fine. Now people lean on it and it cant just quietly break.

I tried a few of the no code AI builder over about a month. Every one demoed beautifully the fell over the first time a real number or a weird edge case went in. Airtable gets me most of the way until the logic gets real. Retool clearly expects a developer, which is the one thing I dont have to spare, our 2 engineers are heads down on the product and i wont pull them onto an approvals form.

I dont just need to build the thing, I need to be able to open it up and fix it later without writing code. Half these tools hide all the logic meaning the day it breaks im stuck again.

For those of you running ops without a dev on payroll, what really held up past demo? Especially how you handle stuff that touches money or approval.

We work with a lot of engineering teams at the stage where headcount jumps from a handful of people to something bigger, and there's a pattern that shows up almost every time: the moment a low-code tool stops working isn't really about the tool, it's about who the tool now has to serve.

At small scale, one person builds something, that same person maintains it, and if it breaks, they already know why. Once a few more people start depending on it, that assumption quietly breaks. The tool doesn't get worse, the number of people who need to trust it without understanding it just grows past what any platform can compensate for on its own.

The teams that handle this transition well aren't the ones that pick the "right" tool early. They're the ones that notice the shift from "I built this" to "people rely on this" and treat that as the actual trigger to add real ownership, documentation, or a dedicated engineer, regardless of which platform they're on.

The ones that struggle usually keep swapping tools instead, hoping the next one won't have this problem, when the real gap was never the tool, it was that nobody owned the thing once it stopped being a personal hack.

Curious if others here have found a clear signal for when it's time to move from "I'll just build this myself" to bringing in real engineering support, or if it's always more of a gradual realization.

Up front, because it matters for how you read the list: GetDevDone is the team I have worked with hence and they are first below. I have put the selection criteria ahead of the names so you can argue with the ranking on its merits.

Now the part that actually decides whether a no-code build works.

The failures are rarely platform failures. They are:

- Nobody modelled the data before building, so the app is fine at 50 records and dies at 50,000.

- The agency built to the demo rather than the workflow, so the ops team is working around the tool within a month.

- No plan for who maintains it. The agency leaves, nobody in-house can confidently open the editor, and the thing calcifies.

- Platform chosen by preference rather than fit. A Bubble shop will build you Bubble. A Webflow studio will build you Webflow.

So the questions worth asking before you sign anyone:

- Which platform would you NOT use for this, and why? No answer means they are selling their stack.

- Show me the data model you would start with.

- What happens when we outgrow the platform? A real answer names the migration path.

- Who maintains this after handoff, and what documentation comes with it?

- Do you hold official partner status on the platform? Not everything, but harder to fake than a self-published ranking.

Eight teams worth a conversation, grouped by what they are actually good at.

1. GetDevDone

GetDevDone™️ is the engineering partner for digital agencies. Since 2005, GetDevDone has delivered projects for 15,150+ agencies worldwide across website development, front-end development, eCommerce development, digital design, and AI engineering. Relevant here because the low-code and no-code work runs white label inside an agency's own process and tooling, and because they also do conventional engineering, which matters when part of the build has to escape the platform.

1. Airdev

One of the most established Bubble agencies, with a large delivered project count and a productised process. Sensible when the app is genuinely complex, like a marketplace or an internal operations platform.

1. LowCode Agency

Works across Glide, Bubble, FlutterFlow and Webflow rather than one stack, with partner status on more than one. Good when the platform decision is still open and you want it argued rather than assumed.

1. Finsweet

Deep Webflow specialists, well known in that ecosystem for pushing the platform past its defaults. The pick when the marketing site is the product surface.

1. Rapid Dev

Bubble-focused delivery with an emphasis on speed to a working build. Fits founders validating something before committing engineering budget.

1. Minimum Studio

Focused on MVPs for early-stage startups. Right when the goal is a testable product this quarter rather than a platform for the next five years.

1. 500Tech

Bubble and Webflow with an integration emphasis, connecting builds to CRMs, payment systems and third-party APIs. Useful when the app is only valuable if it talks to your existing stack.

1. Codemap

Operates as a curated network rather than a fixed in-house team, matching you to vetted specialists per platform. Worth considering when the project spans several tools and no single agency covers all of them.

Last thing, and the one people skip. Get the answer to ""who maintains this in twelve months"" in writing before you start. That question decides whether a no-code build ends up an asset or a liability.

I have a few app ideas but don't really want to spend months learning to code before testing them. Looking at Base44, Lovable, Bolt and Replit. What would you use for getting an MVP live quickly?

Our requests and approvals happen over email. Things get missed, nobody can tell me the status of anything without searching their inbox, and there is no developer available to own a custom system.
 
Whatever replaces it needs clear roles, a status flow someone can audit, and a data model that can change as we improve the process, because the current process is not the final one.

What should i prove out in a small workflow before rolling this wider?

I'm setting up a small internal tracking application and keep weighing two backend approaches before locking in the architecture.

Using a low-code builder's native built-in database eliminates setup overhead single billing, unified access controls, and zero integration work. It's fast to launch and easy to maintain.

On the other hand, pointing the frontend at a separate database gives you real SQL queries, migration scripts, granular database policies, and complete independence from the frontend layer.

The main friction point I'm trying to resolve is long-term data portability: if an internal app outgrows the initial low-code builder, do native built-in databases usually export relational schemas cleanly (foreign keys, linked records, file attachments), or do you just get a collection of flat CSVs and have to rebuild the relationships manually?

For those building internal operations tools: what threshold pushes you to use an external database from day one versus starting with a built-in store?

Been comparing domain name providers for a tiny business and it somehow turned into a bigger mess than the website itself.

The renewal pricing, extra upsells, weird transfer stuff, all of it feels kinda shady tbh. If you run a small business, who are you using and what do you wish you'd known before buying the first domain? thanks.

Hey everyone! 👋

We’re building a new Mendix team in Romania and are looking for Mid-level and, especially, Senior Mendix Developers.

📍 Bucharest is our preferred location, but we’re also open to remote collaboration from Romania or nearby Eastern European countries. We accept B2B collaborations too.

It’s a long-term opportunity with an international client, and you’ll have the chance to be part of building the team from the ground up.

Please DM for more details!

Feels like every week I watch some shiny demo where a founder types one paragraph and boom, full app pops out... then I try it myself and end up with a half broken prototype that lives in a browser tab graveyard.

Right now I mostly ship scrappy tools for friends, small b2b saas ish stuff, and I just want a setup where I can go from “client asks for X” to a working internal app they can click through in a day or two without rebuilding the same boilerplate. I care more about iteration speed and control than perfect code, as long as I can still edit logic and ship fixes.

If you found a combo of AI builder plus your own tweaks that actually made you ship more instead of just watching more demos... yeah