You don't need two firewalls (unless they support failover/high availability) for starters.
Get a decent business class firewall. Cisco ASA 5500 series, Sonicwall TZ 105, pfSense, etc.
Add both WAN connections to the one firewall; I'd probably set them up in at least a failover configuration, but whatever. Your call.
Assuming we're dealing with one L3 switch you've already bought, you can create a VLAN interface for your two VLANs (VLAN 1: 192.168.1.0/24, VLAN interface: 192.168.1.1; VLAN 100: 10.1.1.0/24 VLAN interface: 10.1.1.1). These become the default gateway for the nodes on each VLAN respectively. Whether that's DHCP or not, out of scope for this question.
Create another VLAN, say VLAN 10. 172.16.0.0/29. Set the LAN interface of your firewall to an IP on this subnet (172.16.0.1/29) and create a VLAN interface on same subnet (172.16.0.2/29). Assign a port to this VLAN and uplink into your firewall from that port. You should be able to ping the firewall's LAN interface from within the console of the L3 switch.
Update/create the default route on the L3 switch like so
0.0.0.0 0.0.0.0 gw 172.16.0.1 (pseudo-syntax as obviously it will vary depending on switch make/model, but we want to create a default route to the firewall's LAN interface).
On the firewall, create a route back to your VLAN subnets like so (
192.168.1.0 255.255.255.0 gw 172.16.0.2 and then
10.1.1.0 255.255.255.0 gw 172.16.0.2).
On the firewall, you'll want to look at policy based routing, policy routing, source based routing, etc. (depends on what you get but any half decent router/firewall should support this) but basically you'll want to add a routing rule/policy that looks at the source subnet and assigns a WAN gateway accordingly.
If you don't have a L3 and you're not anticipating a lot of interVLAN routing (i.e. 100s of workstations talking to dozens of servers on different VLANs), don't waste your money on one. Any decent firewall's going to have several physical interfaces (or even one will work with router on a stick, but again, depends on traffic requirements, etc.) and these can take the place of the VLAN interfaces: just carve up a L2 switch into two VLANs like we discussed already, but instead of assigning interfaces (which you likely can't) to the VLAN virtual interfaces, you'll be uplinking into interface LAN1 and LAN2 (or whatever) on the firewall and let it to do the interVLAN routing and/or Internet routing.
Unless you're talking about several switches trunked/tagged together, carrying VLANs from multiple locations, I wouldn't even bother with L2 switches: you could easily accomplish this with just two unmanaged switches, one for each firewall interface. I do prefer L2 switches as there's way more flexibility and management/monitoring options and are reasonably priced typically.