I am looking to build a site that is similar to http://www.lowermybills.com/

I came here to ask what approach I should take with languages, etc. Of course it isn't going to be as big as http://www.lowermybills.com/ but has some similar qualities. All advice is appreciated.

If I wasn't clear in the beginning I just am a little stumped where to start, and would like a little push in the right direction. Thank you all.

Dani AI

Generated

As framed the project (mortgage lead / loan-generation), and as noted, the first practical move is to narrow scope into a concrete MVP. Key scoping questions are: which fields absolutely qualify a lead, whether delivery must be real-time or batched, expected monthly volume, how many lender partners to start with, and what manual review (if any) is acceptable. Those choices determine the architecture, operational work, and compliance needs.

A compact, reliable architecture separates responsibilities: capture → enrich/validate → persist/score → match/deliver → monitor. Capture should be mobile-first with minimal required fields and bot controls. Enrichment (address validation, basic geolocation) prevents low-quality submissions early. Persistence must minimize PII, use field-level encryption or hashing for sensitive values, and keep a flexible metadata column for partner-specific fields. Matching is rules-driven (zip, loan type, credit band) and executed by background workers so delivery to partner APIs or webhooks is resilient and retry-safe.

Example minimal leads table (Postgres-style) to illustrate required fields and the “minimal PII + metadata” approach:

CREATE TABLE leads (
  id SERIAL PRIMARY KEY,
  created_at TIMESTAMP DEFAULT now(),
  source VARCHAR(100),
  first_name VARCHAR(50),
  last_name VARCHAR(50),
  email VARCHAR(255),
  phone_hash CHAR(64),
  phone_last4 CHAR(4),
  zip CHAR(10),
  property_value INTEGER,
  consent BOOLEAN,
  status VARCHAR(30),
  assigned_partner VARCHAR(100),
  metadata JSONB
);

Operational and legal controls matter as much as code. Enforce TLS, encrypt sensitive data at rest, apply least-privilege access, keep immutable audit logs, implement rate-limiting and fraud heuristics, and establish partner sandbox/testing before live traffic. Start with a single partner integration, measure lead-to-close quality, tune form fields and scoring, then scale. A legal/compliance review is advisable before collecting any sensitive financial identifiers.

Recommended Answers

All 3 Replies

The question is way too general. What is your final goal?

I am trying to build a mortgage lead/loan generation system, and would like to know how to go about doing this. I know I would have to learn some type of scripting language(php). But what else to I need to know.

Hope that helps.

You need to know alot of things: you need to be familiar with the business, you need to know databases and database design, you need to know how to secure information flow over the internet, and you need to know web design. You need to be really clear about your intentions and your approach. "some type of scripting language" is far from that. Good luck.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.